Return to release-notes.txt CVS log

Up to [HATARI the Atari ST Emulator] / hatari / python-ui

hatari 2.2.0

User visible changes in Hatari (Python Gtk) UI
----------------------------------------------

2019-01:
- UI version 1.4 (due to Gtk & Python version updates)
- Support both Python v2 & v3
- Fixes to machine setup dialog
- SCC-B output support

2018-10:
- Ported UI code to Gtk v3 by using GObject introspection
  (instead of PyGtk v2 that supports only Python v2)
- Support Hatari's new ACSI/IDE harddisk image configuration
  file settings, along with the old option names

2017-01:
- Fix for systems where "python" is Python v3

2016-12 (Hatari v2.0 fixes):
- Add support for new nModelType config option (with MegaST/STE
  options), but still support also old nMachineType option
- Hatari doesn't anymore support separate RTC option, remove
- Support for keeping ST resolution option is enabled based on
  config file content (it's supported only by Hatari SDL1 builds)
- Initial WinUAE vs. OldUAE CPU core support

2015-05:
- Add support for --gemdos-drive, --ttram option features
  and new tracepoints
- Debugger window supports WinUAE CPU core
- Updated UI version to 1.3

2014-06:
- Add support for --sound-sync, --sound-buffer-size,
  --slowdown, --gemdos-case, --drive-*-heads and
  --drive-* option features and new tracepoints
- Improved option names & descriptions
- update UI version to 1.2

2012-05:
- Add --desktop-st and --force-max options support
  (latter helps video recording of Falcon demos
   doing lots of resolution changes)

2012-01:
- Add microphone and YM voice mixing sound options
- Fix asserts and empty hatari config file caused by
  Hatari v1.6 config variable names changes by changing
  how Hatari config variable types are handled
- Update UI version to v1.1 (mainly due to config change)
- Support spaces in file paths/names

2011-10:
- Replace --slowfdc with --fastfdc

2011-04:
- Support RTC and "keep desktop resolution" options

2011-02:
- Support new tracepoints (AES, DSP, Videl, Crossbar)
- Disasm update for new Hatari disassembly output

2011-01:
- Use new Gtk v2.12 tooltip API
- Support capture cropping

2010-10:
- Improvements to text & key inserting
- Move hatari-console.py elsewhere

2010-05:
- Manual page for Hatari UI

2010-04:
- UI handles Hatari system configuration properly
- New settings dialog for HD dir and image configuration
- Maximum/preferred zoom support to display settings dialog
- Removed --spec512 support
- Option for whether debugger will change to new PC address
  whenever emulation is stopped again

2010-03:
- With the new Hatari --saveconfig option Hatari UI can ask Hatari
  to save its configuration (required by the UI) before the UI itself
  starts, user doesn't need to do it manually anymore
  (if user config is missing or out of date)
- Added --slowfdc support to Floppy settings dialog

2009-09:
- Support for setting CPU level & clock and Falcon DSP type

2009-08:
- Update to latest Hatari 1.3.0:
  - Debug/trace fixes (Hatari 1.3.1 includes these)

2009-07:
- Add Help menu items pointing to Hatari docs & site
- --timer-d support + doc updates

2009-06:
- Move to BerliOS Hatari repo
- Update to latest Hatari 1.2.0:
  - midi in/out, sound freq etc

2008-10:
- Support paths & peripherals settings

2008-09:
- Support for auto frameskip, statusbar and overlay led
- Remove support for multiple machine setups
  (now that run-time Hatari config/saving loading works)

2008-07:
- Support recanim/sound, config load/save and memory snapshot load/save
- First properly working with menus and toolbars instead of buttons
- Can adapt properly also to Hatari window getting smaller
  (works on desktop, maemo/Matchbox WM have still issues)
- Makefile for installation

2008-06:
- Fairly usable version with configurable buttons
- Can adapt to Hatari window size changes

2008-05:
- Loading & saving Hatari configuration and checking
  changes against saved configuration works

2008-04:
- First version with debugger UI

2008-02:
- First version that can embed Hatari window (needed quite
  a lot of testing to find method that works well enough)

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.