[WP34S] New GUI features

[BarryMead]

(01-11-2016 02:32 PM)fhub Wrote:  Hi Marcus!

There's a serious problem for users of the complex WP34s version when using the new 'Import program...' feature:
I'm rather sure that anyone using both (the normal and complex) emulators will probably have the assembler tools and the opcode files in one and the same directory (usually 'tools').
Now the opcode-files wp34s.op and wp34c.op are not compatible, but the GUI does not tell the assembler explicitely which *.op file he should use, and so he always uses the normal file wp34s.op - and this will of course lead to a wrong state file (with wrong or even illegal opcodes), when you import any sourcefile with the complex emulator!

I see 2 possible solutions for this problem:
1) The best way would be to change the opcode table of the complex emulator, so that 'new' opcodes (only existing in the complex version) would not overwrite opcodes of the normal version, but just use 'free' opcode numbers (there are lots of free places in wp34s.op). With this method we won't even have the need for an extra wp34c.op - all opcodes (the 'normal' and the 'complex' ones) would be in the same file wp34s.op.

2) The other method is to explicitely add the option '-op wp34c.op' in the complex emulator when calling the assembler, but in this case you would also have to add the location of the opcode file, i.e. a working option could be '-op ..\tools\wp34c.op' assuming the assembler and the opcode file both are in ..\tools.

IMO the first method with only one wp34s.op for both emulator versions is certainly the better choice (especially because the same problem exists for the QtGUI version, too!), but who can rewrite the opcode addresses in the complex emulator, so that they are at free places?

Franz

Franz: I came up with a completely different solution. I altered the source code for the QtEmulator.h file when I compiled my Qt emulators. For the Complex Branch I changed the "APPLICATION_NAME" to "WP34cEmulator" and I changed "STATE_FILENAME" to "wp34c.dat" and "BACKUP_FILENAME" to "wp34c-backup" and "LIBRARY_FILENAME" to "wp34c-lib.dat". This creates a completely different configuration file for the complex branch named WP34cEmulator.conf which I pointed at the complex branch tools directory. I did a similar thing with the "Bit's" version and it too uses a different op-code file. Now all of my emulators work perfectly and don't step on each others op-code, data, or config files.