Amiga OS 3.2 released

[AndyFC]

Ignorant question, is this only available as physical roms to install, or also digital for those that want to use for emulated Amigas?

The CD contains all the ROM files for the Amiga range.

[Matt_H]

Got my copy of 3.2 last week and have been playing with it in FS-UAE before deploying to one of my real systems. Enjoying it overall--there are some good QOL improvements. The inclusion of datatypes for modern image formats is important. I appreciate the return of comprehensive documentation and the integration into the system is very nicely done. The default DefIcons config and prefs tool is much easier to understand than the one shipped with 3.5/3.9--I feel much more comfortable editing this one without worrying that I'll break something. Thanks to the dev team--I hope we'll see more updates.

That being said, a few issues/notes:
1. Gadget corruption in Pointer and Palette prefs. The FAQ says this is due to a CGX incompatibility, but I'm running on NTSC (with P96/Picasso96API.library 2.363 installed). See attached images.
2. Oops - GUI layout problems in RAWBInfo when NOWORDWRAP is enabled. See screenshot.
3. The advertised TOBACK_QUALIFIER feature of ClickToFront does not actually appear to be implemented. It's not included in the icon tooltypes nor mentioned in the help docs. Am I missing something?
4. I don't care for the thin, blinking cursor in texteditor.gadget. Would prefer to match the GadTools/CON: look as much as possible. Is this configurable through ENV variables?
5. Likewise, I'd also like to configure chooser.gadget to resemble a plain GadTools cycle gadget.
6. The Appearance Settings window in IControl prefs should probably have a Use or OK button instead of a close gadget.
7. Most windows now open directly under the mouse pointer. Is this configurable? I'd prefer to have them either centered on screen or in the upper left (below the titlebar) as in 3.1.
8. The Workbench prefs window is now too tall for a non-laced screen and autoscrolls. I realize screen real estate is an issue given all the window content, but could it be shortened by using 2 columns for the Icons group instead of 1?
9. Similarly, Palette prefs now uses an autoscrolling screen instead of a Show Sample button/window. This makes it harder to see changes in real-time. Could the choice of autoscrolling or button be made in a tooltype? And the Sample window resizable/scrollable so as to not block the controls?
10. Also in Palette, the presets Magic and Thin Menuborders appear to be identical: changing Menu Bright Edges between white and black seems to have no effect. Changing between other colors does have an effect.
11. Perhaps the new Auto-arrange Icons option should not snapshot everything after it executes? All the other icon arrangement options are temporary unless the user chooses to snapshot so it feels like this one should operate similarly. Or retitle it so it's clear from the outset that it will be performing a snapshot, e.g., "Arrange and Snapshot Icons".

Thanks again! Looking forward to exploring this new release further.

[boemann]

Got my copy of 3.2 last week and have been playing with it in FS-UAE before deploying to one of my real systems. Enjoying it overall--there are some good QOL improvements. The inclusion of datatypes for modern image formats is important. I appreciate the return of comprehensive documentation and the integration into the system is very nicely done. The default DefIcons config and prefs tool is much easier to understand than the one shipped with 3.5/3.9--I feel much more comfortable editing this one without worrying that I'll break something. Thanks to the dev team--I hope we'll see more updates.

That being said, a few issues/notes:
1. Gadget corruption in Pointer and Palette prefs. The FAQ says this is due to a CGX incompatibility, but I'm running on NTSC (with P96/Picasso96API.library 2.363 installed). See attached images.
2. Oops - GUI layout problems in RAWBInfo when NOWORDWRAP is enabled. See screenshot.
3. The advertised TOBACK_QUALIFIER feature of ClickToFront does not actually appear to be implemented. It's not included in the icon tooltypes nor mentioned in the help docs. Am I missing something?
4. I don't care for the thin, blinking cursor in texteditor.gadget. Would prefer to match the GadTools/CON: look as much as possible. Is this configurable through ENV variables?
5. Likewise, I'd also like to configure chooser.gadget to resemble a plain GadTools cycle gadget.
6. The Appearance Settings window in IControl prefs should probably have a Use or OK button instead of a close gadget.
7. Most windows now open directly under the mouse pointer. Is this configurable? I'd prefer to have them either centered on screen or in the upper left (below the titlebar) as in 3.1.
8. The Workbench prefs window is now too tall for a non-laced screen and autoscrolls. I realize screen real estate is an issue given all the window content, but could it be shortened by using 2 columns for the Icons group instead of 1?
9. Similarly, Palette prefs now uses an autoscrolling screen instead of a Show Sample button/window. This makes it harder to see changes in real-time. Could the choice of autoscrolling or button be made in a tooltype? And the Sample window resizable/scrollable so as to not block the controls?
10. Also in Palette, the presets Magic and Thin Menuborders appear to be identical: changing Menu Bright Edges between white and black seems to have no effect. Changing between other colors does have an effect.
11. Perhaps the new Auto-arrange Icons option should not snapshot everything after it executes? All the other icon arrangement options are temporary unless the user chooses to snapshot so it feels like this one should operate similarly. Or retitle it so it's clear from the outset that it will be performing a snapshot, e.g., "Arrange and Snapshot Icons".

Thanks again! Looking forward to exploring this new release further.

I'm glad you deficons. I tried my best to create some good categories and a prefs editor that would not scare everyone away. The hope is however to replace deficons with a new simpler system sometime in the future.

3) feature should work. Documentation is lacking - we will fix
4) afraid not as block cursor is reserved for insert mode (though that is not yet implemented)
6) agree
7) I'm not a fan either is all I can say

The rest is noted

[Matt_H]

I'm glad you deficons. I tried my best to create some good categories and a prefs editor that would not scare everyone away. The hope is however to replace deficons with a new simpler system sometime in the future.

3) feature should work. Documentation is lacking - we will fix
4) afraid not as block cursor is reserved for insert mode (though that is not yet implemented)
6) agree
7) I'm not a fan either is all I can say

The rest is noted

Thanks for taking note of my comments. I'll have to play with ClickToFront some more (this could be an emulator keyboard handling issue on my end). I hope something can be done about the texteditor.gadget cursor--the inconsistency of text/string UI elements across the system is... unfortunate. Likewise about windows opening under the pointer. Those are my top two concerns for the moment (pretty good considering the overall complexity of the system, I think!).

The future of DefIcons sounds promising--hope to hear more about it soon. Keep up the good work.

[kolla]

the inconsistency of text/string UI elements across the system is... unfortunate.

I am not surprised by this ReAction.

[F0LLETT]

Have to ask, is any one else having issues with dragging stuff off screen.
It works fine in 3.1.4, but Im unable to get it working with 3.2.

Also, surely you could have done a check to allow PeterK's library to work. May sound stupid, but its put me off setting up OS3.2.

[beller]

Have to ask, is any one else having issues with dragging stuff off screen.
It works fine in 3.1.4, but Im unable to get it working with 3.2.

Also, surely you could have done a check to allow PeterK's library to work. May sound stupid, but its put me off setting up OS3.2.

No problems on either my A!200 or my 4000.  I just selected the option in iControl.

[Steady]

The off-screen dragging must be activated. It is not on by default.

Activate it by selecting the "Can move Off-screen" checkbox in the IControl preferences.

[F0LLETT]

I see, I just thought it would be on by default.
With my 3.1.4 rom, its on by default.

[NinjaCyborg]

It's not compatible with cybergfx so it's off by default.

[kolla]

just don't use the shim with 68000 (guru 8000 0003 if Workbench is loaded)

At last fixed in 3.100 or 42.100 or whatever he prefers… though it still prevents SetPatch from patching copyright notice, boot with 3.1.4 kickstart and 3.1.4.1 setpatch and Hyperion pwns 2019, load the ViNCEd Con-handler “shin”(sic) and Hyperion only pwnz 2018 again. Bug reported a very long time ago, but only triggered a rather irrelevant kneejerk rant from “Der Richter” and no fix. Perhaps whoever managed to convince him about the 68000 bug (kudos btw) could also pass this one on, it looks bad that Hyperion only pwnz 2018 when they should pwn 2019, just because of Con-handler. And who knows what else SetPatch may fail to patch due to this, I have not explored, and my asbesto suit is getting thin when it comes to reporting bugs.

This problem also fixed now, in 3.101 or 42.101 - http://aminet.net/package/util/shell/ViNCEd

Changes made for 3.101:

   ViNCEd now delays loading the icon and workbench libraries, and
   only opens them when they are already in memory. This avoids
   conflicts during early startup if only one of the libraries is replaced
   by LoadModule. While this is potentially a user error, it may be
   helpful to be conservative. ViNCEd now re-attempts to open the
   libraries as soon as the preferences become available, i.e. whenever
   ENV: is created and filled.

Yes - "potentially a user error" is to use the OS version actually released, and not "between releases" OS installed on hard drive of the developer - shame on me

Anyways, kudos again for acting as der Richter-Filter!

[kolla]

No, it doesn't make much sense, noone ever struggled to distinguish these for more than 30 years - hopefully people can still READ!

No, most people don't read manuals. Most developers had to learn this the hard way.

What I meant was reading THE MENUS - hopefully no documentation should be needed to do that, heh.

Things have progressed since 1985 - GUIs are supposed to be self-explaining, albeit this presents an ongoing and sometimes impossible challenge, given the technical restrictions. Radio buttons are a well established paradigm for mutual-exclusive choices in AmigaOS since 1990, so it makes sense to extend it to menus as well.

Not really, we had cycle gadgets and cycle-to-menu - those have been using checkmarks. What do they use now?

Radio buttons can die, they are mostly redundant and just take a lot of space.

The rest has been said.

Are "hidden" volumes (wb prefs) possible to open via the "open volume" in Workbench menu? I haven't seen an answer to that.

C'mon, you must have detected more serious flaws. Even we did.

I don't have 3.2, I comment from what I see people fumble around with on youtube videos. But I understand that shell is almost just as broken as it was with 3.1.4 again in regards to FailAt levels and whatnot... even ThoR isn't using OS 3.2 release shell? So the question is now - how will Amiga Shell be maintaned from here, and how will updates be published? I __VERY MUCH__ preferred it when Thomas lumped updates to Aminet.

[x303]

1. Gadget corruption in Pointer and Palette prefs. The FAQ says this is due to a CGX incompatibility, but I'm running on NTSC (with P96/Picasso96API.library 2.363 installed).

Try the TC020 version of icon.library found on aminet. This also makes any png icons you might have visible again.

[utri007]

OS3.9's unarchiver doesn't work with new Reaction. It gives guru when target is choosed.

[kolla]

Try the TC020 version of icon.library found on aminet. This also makes any png icons you might have visible again.

What does icon.library have  to do with corruption of gadgets?

[kolla]

OS3.9's unarchiver doesn't work with new Reaction. It gives guru when target is choosed.

Shocking. What guru? 8000 0003 again?
Have you tried upping the stack?