![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to release-notes.txt CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [HATARI the Atari ST Emulator] / hatari / python-ui|
Return to release-notes.txt CVS log | Up to [HATARI the Atari ST Emulator] / hatari / python-ui |
1.1 root 1:
1.1.1.2 root 2: User visible changes in Hatari (Python Gtk) UI
3: ----------------------------------------------
4:
1.1.1.7 ! root 5: 2015-05:
! 6: - Add support for --gemdos-drive, --ttram option features
! 7: and new tracepoints
! 8: - Debugger window supports WinUAE CPU core
! 9: - Updated UI version to 1.3
! 10:
1.1.1.6 root 11: 2014-06:
12: - Add support for --sound-sync, --sound-buffer-size,
13: --slowdown, --gemdos-case, --drive-*-heads and
14: --drive-* option features and new tracepoints
15: - Improved option names & descriptions
16: - update UI version to 1.2
17:
1.1.1.5 root 18: 2012-05:
19: - Add --desktop-st and --force-max options support
20: (latter helps video recording of Falcon demos
21: doing lots of resolution changes)
22:
1.1.1.4 root 23: 2012-01:
24: - Add microphone and YM voice mixing sound options
25: - Fix asserts and empty hatari config file caused by
26: Hatari v1.6 config variable names changes by changing
27: how Hatari config variable types are handled
28: - Update UI version to v1.1 (mainly due to config change)
1.1.1.5 root 29: - Support spaces in file paths/names
1.1.1.4 root 30:
1.1.1.3 root 31: 2011-10:
32: - Replace --slowfdc with --fastfdc
33:
1.1.1.2 root 34: 2011-04:
35: - Support RTC and "keep desktop resolution" options
36:
37: 2011-02:
38: - Support new tracepoints (AES, DSP, Videl, Crossbar)
39: - Disasm update for new Hatari disassembly output
40:
41: 2011-01:
1.1.1.4 root 42: - Use new Gtk v2.12 tooltip API
1.1.1.2 root 43: - Support capture cropping
44:
45: 2010-10:
46: - Improvements to text & key inserting
47: - Move hatari-console.py elsewhere
1.1 root 48:
49: 2010-05:
50: - Manual page for Hatari UI
51:
52: 2010-04:
53: - UI handles Hatari system configuration properly
54: - New settings dialog for HD dir and image configuration
55: - Maximum/preferred zoom support to display settings dialog
56: - Removed --spec512 support
57: - Option for whether debugger will change to new PC address
58: whenever emulation is stopped again
59:
60: 2010-03:
61: - With the new Hatari --saveconfig option Hatari UI can ask Hatari
62: to save its configuration (required by the UI) before the UI itself
63: starts, user doesn't need to do it manually anymore
64: (if user config is missing or out of date)
65: - Added --slowfdc support to Floppy settings dialog
66:
67: 2009-09:
68: - Support for setting CPU level & clock and Falcon DSP type
69:
70: 2009-08:
71: - Update to latest Hatari 1.3.0:
72: - Debug/trace fixes (Hatari 1.3.1 includes these)
73:
74: 2009-07:
75: - Add Help menu items pointing to Hatari docs & site
76: - --timer-d support + doc updates
77:
78: 2009-06:
79: - Move to BerliOS Hatari repo
80: - Update to latest Hatari 1.2.0:
81: - midi in/out, sound freq etc
82:
83: 2008-10:
84: - Support paths & peripherals settings
85:
86: 2008-09:
87: - Support for auto frameskip, statusbar and overlay led
88: - Remove support for multiple machine setups
89: (now that run-time Hatari config/saving loading works)
90:
91: 2008-07:
92: - Support recanim/sound, config load/save and memory snapshot load/save
93: - First properly working with menus and toolbars instead of buttons
94: - Can adapt properly also to Hatari window getting smaller
95: (works on desktop, maemo/Matchbox WM have still issues)
96: - Makefile for installation
97:
98: 2008-06:
99: - Fairly usable version with configurable buttons
100: - Can adapt to Hatari window size changes
101:
102: 2008-05:
103: - Loading & saving Hatari configuration and checking
104: changes against saved configuration works
105:
106: 2008-04:
107: - First version with debugger UI
108:
109: 2008-02:
110: - First version that can embed Hatari window (needed quite
111: 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.