Skip to content

Add safety auto-dismiss duration and shorter timeout for launch OSD - #10541

Open
oscarbol09 wants to merge 1 commit into
omacom:quattrofrom
oscarbol09:fix/launch-osd-stuck-timeout
Open

Add safety auto-dismiss duration and shorter timeout for launch OSD#10541
oscarbol09 wants to merge 1 commit into
omacom:quattrofrom
oscarbol09:fix/launch-osd-stuck-timeout

Conversation

@oscarbol09

Copy link
Copy Markdown

The launch feedback toast shown by \shell/services/AppLibrary.qml\ passed \duration: 0\ when displaying via \omarchy-shell osd show. Setting duration to 0 completely disabled \Osd.qml's auto-dismiss timer (\hideTimer).

When launching web applications or applications that delegate to existing browser instances, window-count changes are not always detected by \ToplevelManager\ in time, or signals can be dropped, leaving the notification permanently frozen on screen over the launched application. Furthermore, the fallback \launchTimeout\ was 15 seconds long.

This passes a 3500ms safety duration to the OSD and lowers \launchTimeout\ to 5000ms, ensuring the notification always clears cleanly even if toplevel events fail to fire.

Fixes #10487

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] “Launching X...” notification never disappears

1 participant