Jspeccy v0.91 Changelog:
- Due to the particularities of the system gracietas appetizer I've always had to change the keyboard handling. The truth is now much more like other emulators, but it was not for fun. The previous scheme operated in all systems (Did I ever tell you that I have confirmed that JSpeccy also works on the zLinux operating system?) Except in the most used. Now, both keys are Caps May Shift. The Ctrl and Shift Symbol makes the AltGr key does the joystick fire button selected. Naturally, it has not been easy, again because of it (how strange, is not it?), But the solution I implemented allows use AltGr on keyboards who have or the right of Alt on some keyboards instead for Windows. The other systems have no problems with the AltGr key, well, a shade, the Meta key AltGr makes the keyboards Apple hardware. - Another issue that has brought its tail has been the 128k emulation bug that implemented it in the previous version. I had to investigate several reports of users with problems with programs operating in other emulators but not JSpeccy, and it was always for the same, the contents of register R and memory contention. To make matters worse, these reasons appear to be necessary but not sufficient for the physical computer is restarted and really do not know all the constraints. Having seen, after thinking and asking opinions, I have reached a Solomonic decision: to create a property in the configuration file called emulate128kbug and let off by default. As one of those arcane options if you do not know what it's better not touch it, no way to be changed from the emulator. He who wants to enjoy that functionality to edit the file by hand and put it to true. We have the first right to delete the file JSpeccy.xml we have. - Upon exiting the emulator now automatically saves selected settings of the zoom method and filters. Logically, recovers at startup. This is the second reason to delete the configuration file. - The third reason to delete the above file is the latest. I added a menu where you can select the size of the border that is displayed, configuration is also saved automatically when you exit, along the information if at that time the window is enlarged or not. To the horror of those who do not like reading, this will require some explanation: 1.Borderless: as simple as it sounds. Removes the edge and only see the screen area. Curiously, it looks better enlarged to normal size. 2.Edge Standard provides a border of 32 pixels wide to left / right and 24 pixels up / down. More than enough to see any edge effects. The only program I know that you need more border width is the Defenders of the Earth. 3.Full: painted 48 pixels top / left / right and 56 down. This is what is supposed to be a TV show at best something which I suspect was not ever. 4.Huge: painted 64 pixels left / right and 56 up / down. Is the resolution that describes the ULA guru, Chris Smith, except that the edge is extended horizontally from 48 to 64 pixels. Lets see where do programs boundary changes (within limits of course). I believe it goes without saying that the more pixels are painted, the more work to do the emulator .... - Following the Paralactika Demo (thanks to Radastan for the link), did not work as well as they should, I had to tweak the screen redraw. When all the other demos I had tried were happy with the way he handled the matter, this demo is brutally tough on update times. I mean, quite seriously, that when you want to know if an emulation is good enough, trial of this demo. And talk of times of less than 8 t-states of clarification as to the exact time update (is there a right time?. I think there are 4 t-states ...). - When you open a modal dialog box, stop the emulation and the velocity ratio area is clearly the word STOP painted red. For example, when opening the configuration dialog. - There was an error in the handling of Interface II ROMs when passed to emulate the +2 / +3 and another that recorded in the ROM of IF2 snapshot files to +2 / +3 SZX format and loaded improperly if there was. |
Download: Jspeccy v0.91
Source: Here
0 Comments
Post a Comment