Megadrum Config Tool FEATURE REQUESTS

[Ken Forgettable]

[quote="elrules]Can you explain this a bit more?[/quote]
Erm.

PadGraph.png

[elrules]

Ok, now I get it Ken, that is nice, really nice.

And as I love programming this feature will be a nice challenge

EDIT: i will be editing in my first post of this thread the list of features suggested by you all

[dmitri]

To eliminate the need to do this - http://www.megadrum.info/forums/viewtopic.php?f=4&t=682 - I would like to see an option in MCT to pass incoming from MegaDrum MIDI messages to virtual MIDI ports.

[Rubis]

More of an organizational thing than a feature, but can we change the version numbers to dates? This way we know if our firmware is newer than MCT, which might mess things up.

[elrules]

Ok, nice ideas dmitri and Rubis. Added to the list.

The feature list is growing so big that the new version is going to be a mayor update, or maybe completely redesigned MCT.

I want to start programming soon.

By the way, I have created a project in Google Code, but I couldn´t find the way to upload my code...

[acspike]

By the way, I have created a project in Google Code, but I couldn´t find the way to upload my code...

What did you call the project? I can't find it.

Looks like the mercurial support that I've seen advertised is just by invitation for the moment. So if you want to use googlecode you'll have to start with SVN. No big deal. To upload your code I think you can simply checkout the empty repository with the instructions on the source tab, then copy your project files in and commit them as a new revision.

[userfriendly]

By the way, I have created a project in Google Code, but I couldn´t find the way to upload my code...

What did you call the project? I can't find it.

Looks like the mercurial support that I've seen advertised is just by invitation for the moment. So if you want to use googlecode you'll have to start with SVN. No big deal. To upload your code I think you can simply checkout the empty repository with the instructions on the source tab, then copy your project files in and commit them as a new revision.

Usually you would do an svn import into the empty repository, then move the directory to a backup location and check out a working copy from the repository to a new directory (which can of course have the same name, so when you open netbeans again it won't notice anything has changed).

Downloading Netbeans now. Have been an Eclipse user so far. Hopefully it's not too different.

[elrules]

Don't worry for netbeans, i will explain how to set it up to have the same working environment i have.

About the SVN import, can I do it with Tortoise or netbeans clients? how can i know the URL of the google code server? i have to learn how to do all of this...

[macca2004]

[

As megadrum only transmits midi data to MCT rather than a waveform maybe something like this maybe better. This image show one hit followed by 2 low velocity retriggers.

Just mocked it up quickly so it might not make immeadiate sense.

[elrules]

I like your graphic, macca