ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
carbonfiber has quit [Quit: Connection closed for inactivity]
nerdopolis has quit [Ping timeout: 480 seconds]
zebrag has quit [Quit: Konversation terminated!]
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
mxz has quit [Quit: cya]
mxz has joined #wayland
dcz_ has joined #wayland
sozuba has joined #wayland
sozuba has quit [Ping timeout: 480 seconds]
Company has quit [Quit: Leaving]
hill has joined #wayland
Lucretia has quit [Read error: Connection reset by peer]
Lucretia has joined #wayland
hill has quit []
hill has joined #wayland
hill has quit []
<manuels>
how can I acieve this? how do clients (e.g. csd) move windows?
<emersion>
the compositor will decide for you what's the best spot to show the window
<yshui`>
huh, the xml says `wl_registry::bind` sends a `uint` and a `new_id`, but it actually sends `uint`, `string`, `uint`, `new_id`? did I misread the specification?
<emersion>
yshui`: it does this when the interface is not specified
<yshui`>
I don't understand.. when the interface is not specified, in the protocol xml? what's the condition for these implicit parameters to be added?
<manuels>
emersion the compositor decides to put each new window in the top left board. Which is a bad decision imho
<manuels>
Board>corner
<emersion>
ask said compositor developers to change it then
<manuels>
How do you guys at Wayland think how toolkits like qt should work well with Wayland?
markbolhuis has joined #wayland
<manuels>
No hotkeys, no absolute move no center.
<emersion>
i don't understand the question
<manuels>
Why the heck is Wayland that complicated
<emersion>
in my mind, "does not have bad features" is not the same as "complicated"
<manuels>
I can't move the window of my app. Without writing Wayland specific code.
<manuels>
Thats frustrating
<emersion>
yes, that is by design
<manuels>
How can a move be bad
<qyliss>
You can't move the window of your app at all.
<qyliss>
You can ask the compositor to start moving it.
<manuels>
I can ask the compositor to move it with the mouse, I cant say move it to the center of the screen, right?
<qyliss>
Correct.
<manuels>
How can I center my app then?
<any1>
This is a launcher, so maybe layershell is the answer?
<qyliss>
ah, I missed it was a launcher
<manuels>
Layershell?
<any1>
Yes, there is a special protocol for implementing applications that need absolute positioning and more. It's called layershell
<emersion>
any1: no, they want the user to be able to move the window still
bodiccea_ has quit [Ping timeout: 480 seconds]
<qyliss>
k
<qyliss>
oops
markbolhuis has quit [Quit: markbolhuis]
<any1>
In that case, just overlay it on the entire output and have a floating graphics element in the center that the user can move around.
<any1>
The user can't click anything else, but you can move the "window". Yay :D
<emersion>
that would be a hack
<any1>
Here's an even better hack: Put it into the center using layershell, then if the user grabs it with the mouse, change the size of the layer to cover the entire output until the user releases the window.
<any1>
Is it a hack if it works? :p
<emersion>
Here's an even better hack: On installation, append LD_PRELOAD to ~/.bashrc to a library with special support for common compositors which adds a custom IPC to move windows
<dottedmag>
manuels: Under Wayland it's user who decides what should be centered (by telling compositor to do so), not the application developer.
<dottedmag>
The same applied to X11 to some extent: window managers/compositors that gave users this ability neutered the explicit movement features of X11 protocol without telling applications so. Now it's the rule, not an exception.
jmdaemon has quit [Ping timeout: 480 seconds]
<any1>
emersion: I take it you're not very happy about me trying to think of ways to abuse your protocol? :)
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
Leopold has quit [Remote host closed the connection]
Leopold_ has joined #wayland
fossdd has quit [Remote host closed the connection]
fossdd has joined #wayland
<kennylevinsen>
manuels: window position doesn't necessarily even make sense in all compositors (e.g. VR compositors). As it is impossible to revoke or revise such features once apps depend on them (like with X11), and such feature can easily be abused, Wayland took the simple and safe approach of not exposing such functionality at all.
<kennylevinsen>
maybe requesting "centered" would be okay for e.g. Spotlight like behavior, but then all sorts of apps would start to ask that for no reason so compositors would end up having to ignore it...
<kennylevinsen>
Probably best to just use a compositor policy. In sway you can write a for_windoe rule to center the window of a particular app.
Leopold_ has quit [Remote host closed the connection]
Moprius has joined #wayland
Seirdy has quit [Ping timeout: 480 seconds]
Seirdy has joined #wayland
Leopold_ has joined #wayland
bodiccea has joined #wayland
Leopold_ has quit []
alatiera has joined #wayland
manuels has quit [Remote host closed the connection]