Email or username:

Password:

Forgot your password?
3 comments
Fabian (Bocchi) 🏳️‍🌈

@BrodieOnLinux buttons/elements in CSD/headerbars won't break the dragging of the windows. That's not and never was an issue.

For apps who are stuck, the compositor usually gets this and asks the user to kill that app.

Apps who are frozen are however not movable by the mouse only. This is a problem.

DWD is a silly/broken idea. You'll need to have a fallback if your compositor/WM doesn't support it, otherwise you might have core functionality not available at which point i don't see why someone should do the work and testing twice. If it needs 2 implementations, it's broken by design.

@BrodieOnLinux buttons/elements in CSD/headerbars won't break the dragging of the windows. That's not and never was an issue.

For apps who are stuck, the compositor usually gets this and asks the user to kill that app.

Apps who are frozen are however not movable by the mouse only. This is a problem.

Brodie Robertson

@fabiscafe This is dependent on the GUI framework, and how it handles events. You can't inherently assume things will work properly

Usually is the key take away, and only if the compositor is smart enough to do so

This is a problem

It's only a silly broken idea if it has an inconsistent implementation across different desktops. Or you plan for your app to be used in other environments without thinking that far ahead

Dr. Quadragon ❌

@BrodieOnLinux Actually, you can TOTALLY have it both ways.

Case study.

I use Dino, which is designed around GNOME UI guidelines, which imply CSD. I use it in GNOME, so it uses CSD.

My friend @kafazen uses Dino in SSD environment, namely LXQT. And if the environment is literally incapable of running CSD, the app responds to it by throwing away all the window management buttons out of the header, and letting the server draw whatever decoration it wants to around it. The former header now becomes just an ordinary panel. And it still looks OK. Not *native good*, maybe (if you want it native good, how about using it on the native platform? fresh idea, I know), but still fairly usable.

In well-designed apps built in a well-designed framework this is, basically, a non-argument.

@BrodieOnLinux Actually, you can TOTALLY have it both ways.

Case study.

I use Dino, which is designed around GNOME UI guidelines, which imply CSD. I use it in GNOME, so it uses CSD.

My friend @kafazen uses Dino in SSD environment, namely LXQT. And if the environment is literally incapable of running CSD, the app responds to it by throwing away all the window management buttons out of the header, and letting the server draw whatever decoration it wants to around it. The former header now becomes just...

Go Up