On Fri, Feb 02, 2018 at 06:13:50PM +0900, Carsten Haitzler wrote:
> > So just to be clear, they're going to stop asking E to remove the title
> > bar? If so, great.
> the gtk3-nocsd thing makes that happen.
Sure, but it's a hack. I expect it to break eventually, wouldn't you?
In other words, it works today, but I'm uncomfortable that E doesn't
support this natively and I'm afraid the hack will stop working one day.
> > But either way, E is the most configurable window manager on the planet
> > I'm pretty sure, so it should really have a way for me to ignore an app
> > with broken directives that work against what I want and need.
> the problem is the app still draws whatever it wants inside and that ends up
> looking broken when it also then draws shadows etc. assuming it is borderless.
> it's asking to have somethnig look really broke. the nocsd preload thing is
> a much better.
I agree that the hack makes things look ok, but I also remember E
allowing me to draw a border and putting a 2nd title bar around
google-chrome back it was trying to be borderless for a while
(thankfully it stopped that a while ago).
So, I had 2 sets of minimize/maximize/close buttons. That was really not
a big deal.
I wanted the E title bar so that I can double click on it and collapse
(roll up) the window into the title bar.
Without a forced E title bar, I have no way to do this, and I get very
> i can, but i think it's the wrong solution for your problem, and in general i
> think its the wrong solution too.
It would be a user override for users who care and use cases that
mandate it. If it's not vizually perfect, no a huge deal.
On Fri, Feb 02, 2018 at 06:34:14PM +0900, Carsten Haitzler wrote:
> > Would you please consider re-allowing control of the menubar/border
> > even if the app says otherwise?
> also FYI you want to undo fixes to bug reports:
> so eithr you are unhappy or other people are unhappy.... and
> where you'll find a screenshot of exactly what will happen if you start having
> 2 borders. a window that looks totally wrong. 2 titlebars with a shadow area
> around the inner area.
Forgive me if I suck, but I can't see the screenshots in the 2nd bug and
the first bug gives me
seems like a broken link?
> you're going to have to convince other people don't like this happening that
> being able to have this happen is a good thing. if we allow you to set a
> on borderless windows like gtk ones oyu end up with the above result which is
> far worse than gtk3-nocsd.
Why would they care? It would be a non default option. E would restore
the "set border style" option on those windows (where it is currently
hidden) and let me change the border if I choose to. How would that make
anyone unhappy since they'd have to explicitely ask for it?
> your issue in the end lies with gtk/gnome and their design choices. as i
> mentioned... you won't escape those as time goes on. in wayland it's CSD
> anyway. and that's the future everyone is moving towards. you'll find it
> and harder to fight this, and we will too and it just won't be worth the
Fair point. And how do I get double click roll up there?
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
enlightenment-users mailing list