Re: wAxpander with wAx2
Posted: Fri Sep 08, 2023 7:49 pm
I haven't made changes to the codebase in a while, as it's been pretty reliable. But I did find a bug that could stop partial filename search from working in VICE. It affects VICE specifically because it involves a buffer overwrite caused by the long pathnames that VICE tends to have when virtual devices are used. In hardware, there's not much opportunity for this bug to manifest.
While I was fixing that issue, I made one usability change to the Register Editor that I've always wanted to do. I've never been at the point where I can mentally parse a processor status byte without looking up which bit belongs to which flag, then doing hex math in my head. I know my limitations. And so:
I don't know if this'll help others, but a proper processor flag display will help me a lot. I'm going to spend a few weeks proving the new updates out before committing the changes to cartridges.
(Don't let the set Decimal flag make you nervous. There are safeguards in place )
While I was fixing that issue, I made one usability change to the Register Editor that I've always wanted to do. I've never been at the point where I can mentally parse a processor status byte without looking up which bit belongs to which flag, then doing hex math in my head. I know my limitations. And so:
I don't know if this'll help others, but a proper processor flag display will help me a lot. I'm going to spend a few weeks proving the new updates out before committing the changes to cartridges.
(Don't let the set Decimal flag make you nervous. There are safeguards in place )