Display Settings
As a GUI is part of the bounty, I had to add a configuration page for the full screen mode of course. Up to now, there was a configuration page for the Amiga chipset:
I took a look at WinUAE and (more or less) cloned its "Display" tab:
This is the result:
So now you can change both the full screen option of j-uae (all possible resolutions) and the window size for the windowed mode. At least, if all the hooks are working. So far only the right four frames and the Emulation Speed frame is working.
Btw, this is one GtkTable. Such a table class is missing in Zune, maybe I should convert my GtkTable code one day into a Zune custom class. But not today ;).
Why GTK at all was a question? Because the complete GUI is written in GTK as it was already available for E-UAE. At some places it looks not perfect, but the GUI is quite complex with all the dependencies, so doing a new one in native Zune would be quite an effort.
The whole Display tab is one GTK class, which emits signals if there are changes and exports the values of the settings.
What's still missing in this tab:
- at startup set all values according to the last saved prefs
- hooks for the resolutions and resolution options
- disable all frames, if UAE is running
As a GUI is part of the bounty, I had to add a configuration page for the full screen mode of course. Up to now, there was a configuration page for the Amiga chipset:
I took a look at WinUAE and (more or less) cloned its "Display" tab:
This is the result:
So now you can change both the full screen option of j-uae (all possible resolutions) and the window size for the windowed mode. At least, if all the hooks are working. So far only the right four frames and the Emulation Speed frame is working.
Btw, this is one GtkTable. Such a table class is missing in Zune, maybe I should convert my GtkTable code one day into a Zune custom class. But not today ;).
Why GTK at all was a question? Because the complete GUI is written in GTK as it was already available for E-UAE. At some places it looks not perfect, but the GUI is quite complex with all the dependencies, so doing a new one in native Zune would be quite an effort.
The whole Display tab is one GTK class, which emits signals if there are changes and exports the values of the settings.
What's still missing in this tab:
- at startup set all values according to the last saved prefs
- hooks for the resolutions and resolution options
- disable all frames, if UAE is running
posted by o1i at 13.3.09
6 Comments:
Now I understand...
And I do agree that keeping all the prefs in one only tool looks better indeed, even if that means you have to keep it GTK... You didn't have to be frightened about using it as you seem very well skilled in fact ;-) and your GTK-MUI lib does its magic as expected!
I guess with that out of the way (GUI for screen options) is time for your next step...
What will it be?
Would it be possible to map the GUI to F12 key? Like WinUAE does?
Anyway, great work!
@Hardwired:
First complete the GUI (not yet fully functional). Then release a v0.3. And then get back to the real issue, the UAE integration;).
@Tor:
GUI is a commodity, so you should be able to show/hide it via exchange. But I will try to get F12 working, too. But show/hide needs some improvement for my GDK functions, as the don't check, if they draw on a valid ground and so AROS crashes, if you hide it.
F12 is equivalent to rAmiga in keyboard that don't have left and right windows keys, like many notebooks. Please don't bind preferences to it.
Anyway, I would love to test it and include it in the incoming 1.1 version of Icaros. Would you be so kind to send me a download link? Thanks for your wonderful efforts.
@Paolo:
Ok, then no F12. This should be configurable anyways. But it has only a very low priority for me, so don't expect it any time soon.
Mail with download link of J-UAE v0.3 (release candidate) sent.
Post a Comment
<< Home