This week's contributions to download:
C43 Simulator for Windows: https://classic43.com/downloads/C43_EMU ... _Rel44.zip
Be sure to delete the binary.bin file from the C43 folder prior to running.
Thanks Dani for the help compiling!
C43 DM42 software image file: https://classic43.com/downloads/C43_44L2.zip
Be sure to do CLR/RESET after resetting the first time.
The C43 firmware still requires DM42 DMCP firmware 3.18 or 3.20.
My hardware testing might commence next week again, the replacement DM42 PCB is in the post from SwissMicros... Thank you for the great support Michael.
Let me share my C43 use case story. Skip if you aren't interested in personal shares, as this ain't really Facebook
So, my DM42's problem is that essentially it got stuck two weeks ago as my USB socket promptly broke directly after loading firmware. The calculator works fine except for comms. The point is that I have had the same C43 revision 42 firmware on it for two weeks, so it is the first time since I started the WP43C a.k.a. C43 fork, that I have had the exact same firmware on the unit for a stretch of two weeks. So for me it was sort of a step back and eagle's eye look. I used the C43 on battery power only for the daily tasks in my day office, and this time it remained in my office, together with my trusty HP duo, and I am pretty satisfied on what we achieved as I never even reached for the HP companions on the side desk. I used basic functions mostly (if not exclusively) on the keyboard and used SIG and FIX display modes for various tasks. I found C43 on DM42 a valid replacement for the mundane real life tasks in the office and the kind of work I had to do, for which I have BOTH HP32SII and HP42S on my desk. Yes, I have BOTH of those units on the same desk. Why you may ask, and for that of course there are valid reasons: The 32SII has more functions marked out on keys. I use that but dislike the single line. And the 42S has useful and practical complex operations and the bigger display. And I use that. So my C43 replaced BOTH.
The positive of this was that together with the replacement parts coming from Switzerland for the old DM42, I ordered a new DM42 on its way now. I realised that I can have a C43 that stays in my day office; and a DM42 with me with a different firmware version every day for C43 testing . I recognise though that I soon may retire the HP Pioneer duo to the box.
I added an "equal x/y ticks" button TICKS which forces the X and Y auto scaling to both be the same, as the normal behaviour is to fit both axes to the screen independently. Best seen in the example below:
The Binet graph on XEQM button 12, default auto scaled
The Binet graph on XEQM button 12, auto scaled with TICKS pressed
I became irritated with the softmenu nesting behaviour, or lack there-of, when calling a new softmenu. I made some changes as an experiment. Try it out and comment: that is how we can improve it.
Pressing a menu key, eg. g[ENTER] to call CPX, clears the previous menu and
displays the CPX softmenu.
Calling another menu using a key, eg. g[X<>Y] to call EXP, clears the softmenu LIFO buffer,
and displays EXP.
This, is stock standard behaviour as per the HP42S, but further to this HP42S paradigm, WP43S also supports calling another softmenu from within a softmenu, eg. BITS from the BASE menu, as follows: it stores the previous menu inside a LIFO buffer, and EXIT would return to the previous menus, up to 7 menus deep.
I changed part of the softmenu user interface behaviour as follows:
1. I removed the red section
above, with the result that all menus called will keep on storing.
2. To keep the LIFO buffer from overflowing:
2a. prevent overrun by discarding the oldest item each time the 8th level is reached;
2b. prevent menu entry duplication by checking if a duplicate already exists, (i.e. the second time a user presses the same menu), discarding that prior menu and all menus prior than that, assuming a user does not want to revolve in circles when exiting menus;
2c. even the Simon
game will be easy if you would apply the same rules ... (joke);
3. In all cases Longpress EXIT, i.e. EXITCLR clears the complete menu buffer together with entry modes, etc.
Example 1: buffer already contains 6 menus: EXP CPX BASE X.FN STAT: If you press BASE
again, the oldest entries up to BASE
are removed, i.e. EXP CPX BASE
will be removed
will be added. X.FN STAT BASE
will be the final state.
Example 2: buffer already contains 7 menus: BITS EXP CPX BASE X.FN STAT SUMS. If you press FIN
, the oldest is removed as it is full. BITS
will be removed
will be added. EXP CPX BASE X.FN STAT SUMS FIN
will be the final state.
A consequence of this change, if it works well, and if it works as I expect, then softmenu items within menus, like SUMS and STAT below in the Graph menu, may be re-considered as it is not needed anymore. Calling the keyboard menus will have the same (storing) effect.