Back to Change History

14-0720-1822

This is an initial release to get feedback. Note carefully that many things may change. One that must be highlighted is how preferences are handled. I have not yet written the custom handler I plan, so I am using the default JVM preferences system. On Windows, this uses the registry and MAY WELL FAIL unless you have the correct registry keys set up. This is an issue with the JVM itself. As this will be resolved at a later stage and because it is not that simple a fix, I am not going to supply details. If you are happy to find out what is needed using your favourite search engine, then please feel free to go ahead.

I am particularly looking for feedback from non-Windows users. I have a Windows machine and a Linux machine, so really it is just Mac users I need to hear from.

This version attacks how ComboBoxes are displayed, to bring them into line with the C# version. Whilst I have been able to test on Windows and Linux, as ever, comments from Mac users are extremely welcome.

Current status

The program is stable - it does not generally crash all the time. If you can find a repeatable way to crash it, let me know, providing the console output. Most importantly, if you find a valid TrapKAT V3 or V4 sysex dump that it crashes on, please let me have the sysex dump with the console output from the program along.

The program is almost non-functional. None of the user input fields displays values from the dump. It has the simple functions of converting between V3 and V4 implemented. You can import a global dump into an existing (or new) all memory dump.

Selecting a kit should now also work... this area is still under development, though. The File->Save Current Kit/As... menu item seems somewhat flaky and I have been doing some deep plumbing to investigate. I have yet to properly test the kit dump functions.

I have noticed occasional graphic glitches on both Windows and Linux - possibly also related to the menu changes mentioned above.

Switching between V3 and V4 now updates "all" (I think) of the user interface to reflect the different facilities available. Once I have the menu issue sorted out, I can start properly "wiring up" the sysex data to the user interface.