Skip to content

Add surface intersection observer protocol.#3

Open
outfoxxed wants to merge 1 commit into
masterfrom
surface-intersection-observer
Open

Add surface intersection observer protocol.#3
outfoxxed wants to merge 1 commit into
masterfrom
surface-intersection-observer

Conversation

@outfoxxed

Copy link
Copy Markdown
Member

This protocol is intended to allow clients such as bars and docks to dodge windows that would otherwise be placed over/under them. This is often desired for large widgets and tall bars.

@outfoxxed outfoxxed mentioned this pull request May 23, 2025

@vaxerski vaxerski left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's the use of this over #7?

@outfoxxed

outfoxxed commented May 23, 2025

Copy link
Copy Markdown
Member Author

#7 doesn't have a way to determine the position of a layer surface or the windows relative to it, but that could be included somehow. This one has a much more targeted use case but we could accomplish it both ways.

Also 7 is more likely to be accepted in w-p imo.

@vaxerski

Copy link
Copy Markdown

I see very little chance of this being in w-p and neither do you probably want to discuss for years with folks there regarding all the ""issues"" this has.

#7 doesn't have a way to determine the position of a layer surface or the windows relative to it, but that could be included somehow. This one has a much more targeted use case but we could accomplish it both ways.

Why? With a layer, you know where it is. By protocol. You ask to put it somewhere.

@outfoxxed

outfoxxed commented May 23, 2025

Copy link
Copy Markdown
Member Author

I see very little chance of this being in w-p

I dont see it happening before ext layer is in at least.

Why? With a layer, you know where it is. By protocol. You ask to put it somewhere.

That doesn't work once you have more than one layer on an edge, but its definitely fine in the general case.

@vnuxa

vnuxa commented May 25, 2025

Copy link
Copy Markdown

That doesn't work once you have more than one layer on an edge, but its definitely fine in the general case.

id say most compositors should have some form of tracking layer positioning and size via ipc
and once a compositor agnostic solution is made in wayland protcols then clients could use that instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants