Hello,
Changed transient policy to 0 as a default. Seems to fix the sawfish bug.
Are you sure everyone wants it as the default? This is a serious change that should have been discussed on the list first.
When I first implemented transient dialogs a couple months ago, everyone seemed pleased with that, and this sawfish complaint is the first one ever received about that feature. I think sawfish users can easily set it to 0 in their local configs, while the majority of users will be disappointed to see that unsinkable dialogs are sinkable again.
So I suggest that you reverse that change. And if you want to make it easier for people to set their own dialogs-on-top policy, you could work on the preferences dialog instead, as described here:
http://inkscape.org/cgi-bin/wiki.pl?PreferencesDialog
_________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2f...
On Tue, 2004-02-03 at 23:53, bulia byak wrote:
Hello,
Changed transient policy to 0 as a default. Seems to fix the sawfish bug.
Are you sure everyone wants it as the default? This is a serious change that should have been discussed on the list first.
When I first implemented transient dialogs a couple months ago, everyone seemed pleased with that, and this sawfish complaint is the first one ever received about that feature. I think sawfish users can easily set it to 0 in their local configs, while the majority of users will be disappointed to see that unsinkable dialogs are sinkable again.
I would also prefer that we retain unsinkability as the default.
However, I would like to see a resolution to the sawfish issue before the release, and our three choices are:
1. revert unsinkability
2. introduce custom window decorations that are guaranteed to be present
3. find some constellation of WM hints that makes Sawfish (and other affected window managers) do what we need
[ If it is possible to determine the current WM, an option for any of these approaches might be to construct a whitelist of WMs that will do unsinkability properly the simple way, and possibly introduce workarounds for others. ]
One extra thing that would be nice, based on the testing, is a visually obvious way to sink/hide/collapse these windows. But that's icing at the moment since we're so close to a release.
So... any ideas?
-mental
participants (2)
-
bulia byak -
MenTaLguY