I recently reported that setting windows to be "borderless" does not appear to work in Zune so the "fullscreen" mode in Odyssey is essentially non-functioning.
I now discovered a somewhat related issue. Setting the window height to a specific pixel value does not work at all.
Please note that setting the window width works flawlessly (while the window is closed).
Also, I assume it is known that MUIA_Window_Backdrop does not work.
Wanderer appears to use some creative approaches to try to solve it but if you leave and re-enter the backdrop mode, things may get hidden behind Wanderer that should not be.
If "borderless" (i.e. hiding window decorations) worked, I guess the backdrop issue could be worked around.
AMIGASYSTEMDistro MaintainerPosted
6 days agoI don't understand. Zune stores both the length and width, not only that, Zune also allows you to customise the width and length for each app.
To be clear, each app can have its own width, length, customised background, and even fonts and gadgets can be customised for each app!
AMIGASYSTEMDistro MaintainerPosted
6 days ago@ASiegel @ntromans
I confirm that OWB remembers the dimensions! (I am attaching a video that shows how OWB 32/64bit can store any dimension and retrieve it on subsequent launches).
As mentioned above, you need to be careful how Zune is configured. Zune allows you to store output dimensions and preferences, but you can also configure it so that they are not stored.
Furthermore, if there is no ZUNE configuration (OWB.1.prefs), OWB will use the default configuration (Global.prefs).
To make the configuration of a Zune application permanent, you must save the configuration from the Zune preferences of the application.
Edited by AMIGASYSTEM on 29-09-2025 04:18,
6 days ago You do not have access to view attachments
AMIGASYSTEMDistro MaintainerPosted
5 days agoThe preference files in ENV (Ram:ENV) are temporary and will be automatically deleted after a restart.
The files in ENVARC (Env-Archive) are permanent files.
Each time AROS is restarted, the files in ENVARC will be copied to ENV.
This procedure is also used by AMIGA OS 3.x.
AMIGASYSTEMDistro MaintainerPosted
5 days agoThe problem was caused by ‘ZUNEPREFS.prefs’. If this generic configuration file is present, it will cause apps to ignore both custom configurations and the default ‘Global.prefs’.
Now that everything is working, you don't need to delete anything, except ‘ZUNEPREFS.prefs’ if it is still present. If you have deleted it, it should no exist in ENVARC when you restart.
On AROS One, I only saved some Zune preferences, only for those apps that use backgrounds, special fonts, or special sizes.
All other apps, if they do not find a custom configuration, will use the default ‘Global.prefs’. If ZUNEPREFS.prefs exists, then all apps will use ZUNEPREFS.prefs as the default, ignoring everything else!