MMV Patch Arranger
Posted: Thu Mar 25, 2004 2:24 pm
Hi all,
I am currently working on a 'fairly rough and ready' Voyager Patch Arranger for the PC ("wintel").
Development has been slow, due to other commitments, but I now have something (albeit not a lot) that I would appreciate some feedback on - in order to judge whether it is worth continuing with the current design philosophy.
Please note that this is a patch ARRANGER rather than a patch EDITOR - nothing that fancy at this stage I'm afraid !
It is written in MS Visual Basic 6.0 (as a 'learning project' for me) and has been designed for both 800x600 and 1024x768 screen resolutions (although things get a bit small at the higher resolution - still usable though).
If anyone would like to have a look and provide some comments on current (and intended) functionality then please drop an email to me at:
kevin.bowden@ntlworld.com
You probably won't get anything immediately as I want to properly document the currently implemented functionality, along with the rest of the proposed functionality, and don't want to provide anything for 'consumption' without this.
KB
I am currently working on a 'fairly rough and ready' Voyager Patch Arranger for the PC ("wintel").
Development has been slow, due to other commitments, but I now have something (albeit not a lot) that I would appreciate some feedback on - in order to judge whether it is worth continuing with the current design philosophy.
Please note that this is a patch ARRANGER rather than a patch EDITOR - nothing that fancy at this stage I'm afraid !
It is written in MS Visual Basic 6.0 (as a 'learning project' for me) and has been designed for both 800x600 and 1024x768 screen resolutions (although things get a bit small at the higher resolution - still usable though).
If anyone would like to have a look and provide some comments on current (and intended) functionality then please drop an email to me at:
kevin.bowden@ntlworld.com
You probably won't get anything immediately as I want to properly document the currently implemented functionality, along with the rest of the proposed functionality, and don't want to provide anything for 'consumption' without this.
KB