@whose
So the RKM should be updated to say that every program, which needs a screen bitmap lock more than once at startup or for a longer period of time, MUST react on ICONIFY etc. messages and release any locks on visible bitmaps, if such a message arrives. This involves more work, btw.
You talk as developer, not as user. Currently, when user can't change os settings in realtime, because of "close all windowses" he just in guessing called "what it all about", and that user, will never go on any wiki page to found something where explained what it and for what. Messages from os to user should be self-explained, and contain necessary info. Not some vague "close all windowses". Because not all windowses should be closed. And for user, window its window, app is app. Window can be WB window, and he will try to close them (as i do for few years before understand that its not about WB windowses , but about APP which make stuff wrong).
Regarding the closing of only those applications that are locking the screen, this is nitpicking. How does a user know, which Application holds this lock? The user doesn´t know, so the user must close all windows until the Workbench reset actually happens. IMHO, the wording is quite right, simple and accurate.
But its misliading. You should not close all the windowses ! You should close that one, which come from program which do things bad. "Windowses" sounds for users (and for newbes too) as windowses, and he will try to close WB windowses, or whatever, which is wrong. As he should close APP which do lock screen. And because of that warning misleading. User can like a madmann close all windowses which he see, but there can be some app which didn't show window as window, but still lock the screen. I.e. its all about APP which do things bad, and warning should point out on that. Not on vague "all windowses". There can be one, or two, or more bad , but not all of them, and message should mean that, so any new user will get what it mean without any needs to learn aos internals and be developer or whatever. I even didn't point about "except drivers", which make system warning be misleading twice, because user for sure will think that its about WB windowses only.
Users who are feeling not good with this should contact the software´s developer to change the behaviour of the software. They will know which program it is, right in the particular moment they close the window of the faulty application
Like we live in ideal world.. No one will contact anyone, because users mostly give a shit about, they have their time, and for them enough that they buy os4 and use it, and they not want and will not contact anyone (maybe only in some lucky for us cases). They will just know (as i know for years before i udnerstand the roots), that "you can't in realtime change system settings, because it bring warnings about some strange windowses which i need to close, while before i close all WB windowses and it didn't help, so os4 just cant change settings in realtime, pity". And that will be final understanding of pure user who first time (or second if we will be lucky) run os4.
And you say "they will know what app is it, right when they close faulty application", but that mean exactly that ! They _found_ faulty app. But warning says "close all windowses" : its wrong. Not _ALL_ windowses should be closed. Its app should be closed which lock screen. Not all wnidowses of all other apps. Warning should point like "try to close all the apps to found faulty one" or something. Not like it now, which can be undersanable by us, who already break our minds by years of amigaos, so we think that bad messages its good message for users
Is it really that hard to change Picasso96Mode to use ReAction instead?
I think no, but is there free devs who will do so ? Taking aside that devs want to depricate p96 (but that will take years as usual), there is just no devs who aren't busy with anything else. But i think if whose will write p96settings replacement in reaction, then os4devs will happy include replacement for meanwhile till p96 not removed totally
). trixie´s guide to screen programming on OS4 Coding is a really good source for hints about screen locking and the problems one could run into. Should have been included in these chapters already, IMHO.
