Activity for thrice
-
thrice committed [1f5c8d]
update symbols from file on enter pressed
-
fix 3 widget hexpand bug
-
fix holes where filename can be blank, resulting in NULL table
-
sort symbols list on label
-
remove filter/search thing, enable the native search on the list view
-
set initial size of symbols dialog to something vaguely useful
-
tidy ups
-
more work on the GUI
-
start on the filename/reload for symbols
-
start symbols GUI dialog
-
updates to memory browser and debugger to allow them to use symbols
-
switch parser to regexes
-
add save, pause and mute toolbar buttons
-
make toolbar labels switchable
-
use glib hash table
-
crude parser added
-
get the symbols parser call into place
-
add address parser sources
-
add toolbar separators to recreated and speed control
-
centre RZXS toggle button label
-
kill off double clicking on the speed spin button
-
tidy now working speed button
-
repair lost options->toolbar update
-
get speed label in an event box
-
more tweaks to speed toolbar widget
-
tidy compiler warnings in toolbar code
-
enable the toolbar speed control
-
make a simple SVG icon work in toolbar
-
set toolbar visibility from settings on startup
-
add toolbar options setting
-
recreated zx toolbar button working
-
fill out the toolbar a bit
-
update README
-
wheel and toggle behaviour as required
-
get scroll events working on the statusbar speed label
-
remove unneeded enter/leave event handler
-
make statusbar speed label clickable
-
Merge remote-tracking branch 'upstream/feature-138-larger-keyboard-image'
-
Merge remote-tracking branch 'upstream/master'
-
Merge remote-tracking branch 'origin/master'
-
merge upstream master
-
Merge remote-tracking branch 'upstream/master'
-
switch from my keyboard graphic to the one FredM uses in the Mac Fuse build
-
add new keyboard graphic file
-
Update README to make my changes clear
-
Make my mods clear in About dialog
-
Merge 1.5.7
-
Step over button in debugger
-
Previous value of PC in debugger
-
restore original step next function, make step over separate
-
rework step to step-into and step-over
-
Merge branch 'memory_browser_offset_fix2'
-
That's better. The SF merge request dialog only shows the commits you're requesting be merged after you've hit the send button. You can't tell if you've made a mistake until you make it! Anway, this looks right now and I attach a screenie which shows the before and after dialogs.
-
Make the memory browser offset entry wider (v2)
-
make the address entry field wider
-
Make the memory browser offset entry wider
-
oops, that didn't work out as planned. :o} I think I've requested a merge from the wrong branch. Let me work out how to cancel this and try that again!
-
Make the memory browser offset entry wider
-
make the address entry text widget wider
-
trivial merge conflict in debugger gui
-
Merge remote-tracking branch 'upstream/master'
-
Step over button in debugger
-
add stepover button, tidy debugger's next function
-
Merge branch 'feature-128-previous-pc'
-
debugger step over button
-
fix syntax err
-
tidy up some of the code
-
more drag and drop tidying up
-
tagged source in debugger, initial
-
1.5.6 regression: save binary no longer saves 64KB
-
I had another go. :) I added a flag to indicate the validity of the previous PC value. This flag is set false when the Z80 is reset, then set true when the PPC value is set to something. The GUI shows the PPC value as "------" when the flag is indicating an invalid PPC. The snapshot code does a Z80 reset, and the RZX loader loads a snapshot, so unless there are any other holes I'm unaware of this should be OK. I wasn't sure what to do about the PPC debugger value. The interface only allows for 16...
-
use flag to indicate previous PC validity, couple of bug fixes
-
Um, yes, good question. These are the sort of nuances I'm not familiar with. :o} None of the numbers the value can hold (0-0xFFFF inclusive) would make sense, so I think the correct thing to do would be to add a flag indicating that the previous-PC is valid or invalid. This could be a separate variable, or I could change the type from regpair to something wider so it could hold a sentinel value. I prefer the flag option. The GUI can then reflect the status (printing "----" to indicate invalid). Is...
-
Previous value of PC in debugger
-
previous PC in debugger, initial
-
Small update: I took the calls to SAVE_PREVIOUS_PC out of the RET and RST macros. They weren't right there, producing off by one errors in the PrevPC value. As for the interface, yes, it's tricky. The debugger variable value is neat but rather useless! It's a terribly inconvenient way to get at the value. I'm still using my hacked debugger window, which shows it at a glance. The thing is, the PrevPC value doesn't really fit anywhere in there. It's not a register, so can't go in with the registers,...
-
I was looking to learn about the fuse codebase and homed in on this ticket in a rather arbitrary way. How would saving the previous PC register work I asked myself? I started investigating, and from an initial parse of the fuse code it looks fairly straightforward. In the z80 structure I created on of these: regpair previous_pc; In the z80_macros.h header I created these two macros: #define PPC z80.previous_pc.w and #define SAVE_PREVIOUS_PC (PPC=PC) then added a SAVE_PREVIOUS_PC call to the existing...
-
Goodness. I like your service... :) That works a treat. In my game loop code I added this where I appear to have a problem: void gl_assert(void) { while(1); } ... case MOVE_LEFT: gl_assert(); game_state->runner->xpos--; then pick the address of the assert function from the compiler's map file with this: PYTHONPATH=. ./fuse --debugger-command "break $(grep -P '^_gl_assert' zxrunner.map | perl -ne '/(\$\w\w\w\w)/ && print "$1"')" I tweaked your little python script to dump the whole memory space (I...
-
Allow the Spectrum to talk to the emulator
-
There doesn't seem to be anywhere on the SF interface to say thanks, so I'll post here. Thanks! Got it running on Ubuntu with an Infinity In-USB2 foot controller, generating key presses to start/stop and skip back and forth in VLC. Works a treat. I was a bit stuck at first because it defaulted to an incorrect input device (11, mine came up as 5). Would it be possible to improve this? Say, unplug the controller, scan the devices, plug it in, scan again, and see what's appeared? That would be possible,...
-
The RZXS keyboard has been in the main build for a year. I haven't actually tested 1.3.8, but it's working fine with the 1.3.5 build i happen to have on this box in front of me. The switch on the back should be in "layer A" mode, and you need to enable it via Options->General->Recreated ZX Spectrum. If you open a regular text editor on your PC and press '1' on the RZXS keyboard you should get "ab" printed. If all that matches your setup, ask on the mailing list or open a support ticket.
-
OK, I gave that a run on the same VM setup as before. I pressed (and released) A,...
-
OK, I gave that a run on the same VM setup as before. I pressed (and released) A,...
-
Windows isn't my thing, but I have an old WIn7 virtual machine to hand, so I ran...
-
The 02 patch applied cleanly and appears to work. I haven't tested every key sequence...
-
Can confirm that with a very slight tweak to pick up a header file from the right...
1
