On Tue, Sep 08, 2020 at 08:56:49AM +0100, Carsten Haitzler wrote: > it could be a race where gtk/gnome terminal is setting role AFTER it shows the > window... so it's a pure luck/race condition that by the time e responds to > the > map request and reads the window properties role may or may not be set by that > time. that is a possible reason. as i mentioned already... try with another > terminal that i'm pretty sure is doing things right and see if the issue > happens there too. elimination of possible things.
I see. Is there an easy way to find out if the properties are being saved on disk properly, to make sure the lock properties are being saved? Also, with the new E that saves current state before it restarts, is there a way to make it behave like the old E and tell it "please apply config saved settings to all current running windows?" Obviously I could revert to E 0.23 and that'll fix my problem, but you told me enough about how I should be running E 0.24 :) I hear you on switching terminals, it'll be my last option. I don't actually like gnome, but the termeinal checks a lot of checkboxes I need. Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Home page: http://marc.merlins.org/ _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
