You are not logged in.
This is a very annoying thing. I just moved from using Qt4 to Qt5,
and was distressed to discover the very weird fact that on my
system (the most recent xfce desktop from Fedora 20), qtcreator
and qtassistant, as well as the apps I am writing, automatically
raise when they are clicked on their interior, despite the fact
that the settings are set to have them only receive the focus,
and not to raise.
No other applications do this. Only qtcreator and qtassistant
and the qt5 apps I am currently writing to this.
Also they do not do this under kde. And they also do
it under f19 on my netbook as well (also
running xfwm4 version 4.10.1 (revision 3918e6b)).
I sure hope there is some fix for this. I typically use
many apps fullscreen with a small app over top of
part of their screen real estate, moving focus back and
forth.
Thanks for any ideas.
Offline
Might want to ask the developers of those two qt5 apps if they have done something that breaks the freedesktop.org standards? I don't suppose it's any likelier than any other cause, but one never knows.
Then again, unless you find a non-qt5 app that exhibits the same behavior under XFCE...
Regards,
Offline
Might want to ask the developers of those two qt5 apps if they have done something that breaks the freedesktop.org standards? I don't suppose it's any likelier than any other cause, but one never knows.
It is not just those two qt5 apps, it is every single qt5 program compiled in the simplest way, including all their demos and my own programs. It is qt5 by default, not any specific apps.
I have also since discovered that the correct behavior is observed in openbox.
I will try to find where to ask them about this (the qt5 developers). There does appear to be a place where people are complaining about something similar but I don't know enough about this to see how they are related.
Offline
Maybe they've decided to take a page from the GT3 developers' book, lol, and set things up so that version updates start breaking functionality - I guess they could all call it a feature, sort of a way to make sure that people realize that they've been, err, hit with an update. And if it is in the "framework," that would explain why it is an across-the-board thing, so to speak.
Like someone once said, you cannot make an omelet without breaking a few eggs. Now that I think of it... It was Iosif Vissarionovich Stalin (Ио́сиф Виссарио́нович Ста́лин), IIRC.
I'm guessing (but, of course, do not know) that, since Openbox doesn't show the issue, that it might be something simple, perhaps the name of a setting was changed or something. Please let us know if/when you discover more information on it.
Regards,
MDM
Offline
[ Generated in 0.007 seconds, 7 queries executed - Memory usage: 533 KiB (Peak: 533.84 KiB) ]