showing the tape window for fastload ROMs would cause the debugger to
crash. this was because the tape data was empty and the waveform plotter
expects some data
this solution removes the tape window entirely, and the menu entry, in
the cast of fastload supercharger ROMs
previously, throttling of thumbnail generation was controlled by the
clock. for fast running emulation this wasn't a problem but for slower
emulation (eg. ACE) this was ineffective and caused multiple thumbnail
request to queue up
this revealed a general inefficiency, even if it wasn't noticeable in
"normal" circumstances
the new throttling method prevents more a thumbnail request to be
generated if one is in process
the reset statistics button moved to sit alongside kernel focus option
checkboxes moved to their own line. all controls are now visible even
when the window is resized to its smallest
resizable; guidelines; hover cursor
thumbnail removed from tooltip and now appears as faded image alongside
hover cursor
timeline thumbnail option moved to the debugger tab of the preferences
window
fixed bug in how scanline trace was plotted
thumbnail animation in ROM selector would not update satisfactorily if
the polling time was limited. for example, in the debugger when the main
emulation was not running. polling decision now takes into account
whether ROM selector is open
tooltip indicator in menu bar. clicking will toggle. same preference can
be toggled in the debugger tab of the preferences window
global setting can be overridden by holding down the shift key
setting will be automatically saved on exit
tooltip settings for individual windows removed (disasm, performance,
source windows)
added slight transparency to tooltip background
for example: a hotkey is assigned to a coprocessor window and a ROM
is open that does not have a coprocessor. in that scenario, the manager
would struggle to focus on the correct window causing a flickering of
the selected window
"captured running" is a new name to describe when the debugger is
running the emulation and the input is captured. it can be
entered/exited with the ESC key (and other ways, but principally the ESC
key)
"fuzzy window matching" renamed to "window searching"
pressing CTRL+SHIFT allows the user to bring a window to the front by
typing in the window title. as soon as the entered string is unique the
window is selected
a search preview is shown in the menu bar while the CTRL+SHIFT
combination is held down
screenshot modes are now divided into single, motion and composite
'single' works well with regular displays (ie. Pitfall etc.)
'motion' works well with some flicker kernels (eg. zookeeper and similar)
'composite' meanwhile is very good at creating images with most flicker
effects eliminated (eg. Wenhop) and capturing motion (eg. Wabbit)
pixel information is accumulated before passing through CRT shaders.
this results in better colour blocking from flicker kernels
not perfect but an improvement in many respects
the separation effect between pixels seen in flicker displays (zookeeper
brick effect being the best example) is currently lost
brightness of captured image is an issue
command line now only accepts true/false as options. previously, the
options were aimed at allowing different syncing methods with the
monitor but that's not needed now
this is a quick fix. a more thorough examination of when and how the
pixelrenderer.Resize() is called would be good. current fix has been
applied in the screen implementation of pixelrenderer.NewFrame()
function, which may be the best place
RMB is used to capture mouse for paddle input. but the RMB is sometimes
used in conjunction with emulation windows
if the mouse is over the TV screen then the mouse is captured as normal,
even if a window is open
it was casting to the incorrect type but without any check on whether
the test suceeded
also, changes to the stackpointer in 057dddb02 meant that the RAM window
tooltip with regards to SP information was broken
developer package doesn't no longer deals with "disassembly" except to
provide a reference to the disassembly interface provided by the
cartridge. the more accurate description of "instruction" is now
preferred
32bit instructions are distinguished by the Size() function of the
cartridges disassembly interface. this is more flexible and makes the
interface to the coprocessor implementation (ie. ARM) less clumsy
clarified hi/lo words of 32bit Thumb2 instructions
removed tracker from the lazyvalues package. access to tracker
information is now done through a "borrow" function
moved volume change logic from win_tracker to main tracker package
AudioTick() function in tracker interface accepts TrackerEnvironment
instance. tracker implementation differentiates emulation instances and
records AudioTick() information accordingly
imguiSelection type introduced in the previous commit to help with the
tracker. the previous multiline selction method used for the source
window was therefore made obsolete
better visuals for tracker window
sketched in idea for a tracker "replay" feature that will allow a
selection of audio output to be replayed. it works in principal but is
not currently used
