ChrisH wrote:
@broadblues
Auto-Close was NOT ticked in MUI prefs. To be honest I didn't know it even existed (it is easily overlooked), and IMHO auto-close should be the default behaviour.

With Auto-Close ticked, SimpleMail's screen does close correctly when CygnusEd's "visitor window" quits after SimpleMail quits.

As far as I can tell, testing with the latest MUI, the default now is to have autoclose ticked.

broadblues wrote:
@Amigo1

is autoclose option slected in the MUI Screen prefs?

xenic wrote:
The whole public screen mechanism and "Screens" created public screens work fine on my system. I don't like Ringhio and don't use it. It opens small notification messages that don't look or act like standard Amiga Windows. They are just small colored blocks with text that appear on the screen background. I think the Ringio notifications look like they belong in some other OS. There are clearly defined mechanisms for visitor windows and requesters on public screens but Ringhio messages don't act like normal windows or requesters and don't appear to be well integrated into Intuition. The problem is with Ringhio and not Intuition or Screens preferences and I think that patching CloseScreen() is a misguided attempt to compensate for a Ringhio problem. Without Ringhio, my public screens (whether program created or Screen prefs created) all work as they should. I think Ringhio should use system compliant requesters instead of the current method.

This bug still appears to be present in Update 3. Having just removed BetterCloseScreen from user-startup, I've had to reinstate it as Ringhio notifications are still causing closing screens to get "stuck".