I believe the ROM file used is tied to the KML file. When i try to open it, the loaded rom is the one provided with the emulator (2.10) and of course with Port 2 empty except equation library and periodic table.Īpparently the emulator refuses to load roms not provided with the app. I copied the state file and rom file (2.15) of my emulated 50g. Once I store something in port 2 and restart emu48 (even with explicit save state), the emulated calculator will perform a warmstart and everything in port 2 is lost (except for the default equation library and periodic table). (04-08-2019 11:46 AM)Marco Polo Wrote: (04-08-2019 11:01 AM)SammysHP Wrote: When emulating a 50g with 1.3 I'm not able to store something in port 2. So just wait for 1.3 and it should work better.
#EMU48 WINDOWS 7 CODE#
I just verified this with the code currently in github (but not yet released) and it works as expected.
#EMU48 WINDOWS 7 FOR ANDROID#
The next version, 1.3, now lets you set Emu48 for Android to either use the KML's default color (gray in this case), or black, or the status bar color (which is a dark shade of gray, almost black, on my phone). Since 1.2 (I think) it now respects the Color attribute in the KML file, which is currently often the gray value that I set them to in my original scripts, which was good for their original intended desktop use, but admittedly is not ideal for the Android version. I liked it much better without the bright gray, is there a way to get rid of it again, for all built in ones? (preferably a global setting, no fiddling with all individual kml files an android please )
#EMU48 WINDOWS 7 UPDATE#
(04-04-2019 07:53 AM)Lode Wrote: The previous version (before 14 march update I think) of the app had black background (or at least one that was not noticeable, which was good), now it's bright gray (there are now two thick bright gray borders left light and right on android, for all built in calculators/skins/kml files) Replacing int with bool made data structures more compact, but it also caused compatibility headaches where data structures are persistent, i.e. When I changed the project from C to C++, I started using bool instead of int where appropriate, but mostly in new code, leaving old code alone. In Free42 I used int for bool originally for that exact reason. This convention survived for a long time, because it took so long before C adopted bool - I think bool only became an official part of C in the C99 standard. In early C, there was no dedicated Boolean type, so they used int instead, with the convention of saying 0 = false and 1 = true (or any nonzero value). Using an 8-bit quantity is still wasteful, but a common compromise since it's usually the smallest addressable unit. To save space? Using a 32-bit type of which you're only using one bit is rather wasteful. (04-04-2019 12:16 PM)ijabbott Wrote: I wonder why BOOL was defined as signed char for the Android build? If it was for iOS I could maybe understand it.