- Use more appropriate fsel var name instead of file
- Fix rest of PyGTK deprecation warnings by:
- changing how GtkDialog is created
- not using monospaced font in address entry
- using GtkTextView instead of GtkLabel to get text widget
with monospaced font
- Remove left/right arrow keyboard shorcuts for memory address
changing as then that would be triggered also when editing
the memory adddress
- Call set_dumpmode() method at start and dump() after options dialog
so that debugger window is immediately in right size
Fix: specify for Gtk.FileChooserButton() that label is to be used as
file selector title.
Allow title to be specified also FselEntry, not just for file
selectors gotten from FselAndEjectFactory.
Use labels in front of options (in settings dialogs) also as their
file selector titles, and have all of them ending with ':' for
consistency.
ConfigStore does now stricter section & key checks against Hatari
config, which broke debug UI config saving. Because debug UI is
likely to go away at some point (doing debugging from another process
has too many restrictions), do minimal fix (don't save follow-pc
option).
There are some additional changes on top of Gtk v2 -> v3 changes
coming from switching from static PyGtk bindings to GObject
introspected ones.
- Extra data can't anymore be stored to objects. This caused
a lot of changes in Table widget handling -> column needed to
go into helper function parameters
- Alignments are now given as properties to widget constructor
instead of needing to use a wrapper object
- Focus flags are now also given as properties
- Some other changes widget constructor parameters and whether
they're optional or not
- table dialog helper supports multiple columns
- table helper for radio button group items
- use above in machine config dialog
- add CPU level & clock and Falcon DSP support to machine config dialog
and configuration handler
load/save features. If config changed in UI, give a temporary
config file to Hatari whenever it's re-run
- Fullscreen isn't anymore a toggle as user cannot use this
option if Hatari is fullscreen... Removed fullscreen config
option handling as it will be changed also directly from Hatari
- To support drag&drop for the UI, it forwards non-option args
(floppy name) to Hatari from the UI command line
- Disk image and joystick settings to separate dialogs
- Add dummy paths and peripherals settings dialogs
- Check that Hatari supports --control-socket argument
- Make dialog run() methods more consistent
- Python code compatible to Python 2.4 (I'm testing with 2.5
which accepts '()' for classes not inheriting anything) and
wrapper scripts to older SH (use exit when outside func body)
for all the required hatari variables
- list (in comment) which Hatari variables are not yet supported
- disable Hatari internal quit confirmation when starting Hatari
- adapt to the new Hatari joystick settings option
- add handling for the new Hatari disk options
- add Hatari peripherals dialog (uses table helpers)
and move disk & joystick settings there
- refactor hatari.py a bit so that debugui.py can be
given options with which it should run Hatari
- comment code more
with keys named the same (shortcut and joystick sections),
needed to rewrite config handling to take this into account
- added joystick emu selection
- apply doesn't close trace settings dialog, only close will do
- don't derive from HatariUIDialog unnecessarily
- change helper methods that don't use other class methods
or object variables into functions
- prefix internal methods with "_" is is python convention
- add docstrings to methods
- move common / helper functions from dialogs.py to new uihelpers.py file
- add there create_toggle() and create_button() and use these in debugger
and hatari UI instead of methods
- move class variable constants to their own Constants and UInfo classes,
this makes sharing them more explicit
- associate HatariControls instead of inheriting it in HatariUI,
this makes the class roles more explicit (but there are some less
clean things still)
- prefix all internal callback methods in HatariControls with "_"
(which is a Python idiom)
in preparation for additional memory area monitoring windows requested
by Nicolas
- ask user whether Hatari should be killed instead of just killing it
- fix OO-style issues reported by pylint
- add options dialog for number of lines on screen
- use different address skips in memdump & disasm modes
- get distinct lines from hatari instead of concatenated data
- remove "Default" button as useless (when monitor windows are added)
and set Registers as default mode (+ get address from PC register)
- lots of fixes to how address changes are calculated
- make register dump just one of the dump modes
- fix the dump widget to monospace font and make it not to resize
the debugui window if the widget is smaller than the available space,
only when there's too little space
Eero Tamminen