-
-
Notifications
You must be signed in to change notification settings - Fork 60
font-viewer: Bring the window to the front when triggering the app #780
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
If the app is already open, we need to tell the desktop that the window has been triggered, so it can either bring it to front, or notify the user the window claims attention. This fixes the cases where the font viewer is already open and gets triggered again, e.g. by opening a font or launching it directly.
Got a build failure in Meson with an error at the end of this string of test, appears to be unrelated to this PR. The autotools build finished without issue:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works, stopping the odd back button behavior if fonts are clicked on in /usr/share/fonts in caja while the font viewer is open.
Given the file involved, I am all but certain the meson build failure is unrelated to this, the autotools build went fine and I was able to test the new build of mate-font-viewer. Approving
The travis fails are also unrelated to this PR:
|
Wait, this PR has nothing to do with that issue, which is #777 (included here though). What this should fix is that if you open repeated fonts like you say, the font viewer window is brought to front each time. |
This did indeed bring the font viewer window into focus on clicking any font
|
If the app is already open, we need to tell the desktop that the window has been triggered, so it can either bring it to front, or notify the user the window claims attention.
This fixes the cases where the font viewer is already open and gets triggered again, e.g. by opening a font or launching it directly.