[WP34S] New GUI features

[BarryMead]

(01-08-2016 02:21 AM)pascal_meheut Wrote:  And even this should not be necessary as a copy of tools is inside the distribution and should work out of the box.

I am sure this is the case if you choose one of the pre-built distributions. I always use a custom compile changing a few file names in QtEmulator.h so that the Help/Manual menu item shows my Personalized 3.3 pdf manual that I bought from Walter, and so that the three versions of the Qt emulator that I compile don't step on each other's config/data files. I compile 3 separate Qt Emulators, one with "Bit's" Optimizations, one for the Standard WP-34S, and one for the Complex branch. I also point the separate config files to separate Tools directories so that the assembler uses the right op code file to generate matching binary data for each Emulator. I tested everything and it all works flawlessly. I also re-flashed my calculators with the latest firmware (with Bit's Optimizations) and confirmed that all of the import/export features work and generate the proper op-codes. This new Qt Emulator has nearly every feature I ever wanted. Thanks to Marcus, and Pascal for this giant leap forward!

Marcus: After some additional testing, I did discover an issue with the "Calculator/Export Program" menu item. As a test I pointed the program counter at the 'TVM' program in flash, and copied that
program down to RAM with the P.FCN PRCL command, then I exported that RAM program to a file called TVM.wp34s. When I tried to import that saved source program I found that it caused the assembler to error out. It seems that the "Export" process isn't generating [space] or [narrow-space] macros within [alpha] strings in the exported source files, and the assembler does not recognize a space character ' ' in an [alpha] string, but requires the [space] or [narrow-space] macro instead. I thought you would like to know as soon as I found the issue, so you could perfect the operation of the Export feature.

I found a similar quirk when I tried to export/import the digamma.wp34s program. On line 75 the export failed to prefix the "CONJ" op code with "[cmplx]CONJ" so the re-assembly failed.

Do you know of any source code level test files that they used to validate the Assembler/Disassembler? Perhaps we could re-use these test files to validate the Export/Import features. It would be good to have a test file which includes an exhaustive list of Op-Codes from every sub menu, and also includes every parameter/argument type allowed to be sure they are disassembling and assembling correctly.