Wayland, Windows, MacOS: Popup Implementation#4543
Conversation
facdfde to
87f6327
Compare
Reason: Because a normal window can have a parent window as well, like a Dialog
Reason: otherwise the child surface is anchored to the center
Reason: otherwise the height of the client side decoration is not considered and therefore the location is shifted
Reason: There are multiple pointers to the smithay popup. Once in state.windows and one time in the popup object it self. Just dropping the popup object releases only one pointer but we have to notify the state to release also the other
…he position Reason: Much easier in the resize handle
Reason: we have to call resize to initialize the viewport to map to correct window size
Reason: Because wayland or the event loop could destroy the popup and therefore it is anymore available
|
In 90ebef0 I implemented the correct popup order destroyment. I had the problem that the Popup Item it self contained a window state and therefore it got not delegated to the compositor that the popup shall be deleted. This I fixed in ac4a329 by storing only a Weak pointer of the window state in the Popup struct ( |
I like that you also came to a conclusion I had for the window storage, as in basically user has some handle but the Window itself is only owned by winit. I'll think about it a bit since we want to plug it into the current design, but generally, I think that's how it should be, honestly, even though a lot of folks disagree with me on that matter... |
Reason: Otherwise it will not be dropped
Thanks! Just let me know whats your decision here |
| mem::drop(window_requests.remove(window_id)); | ||
| mem::drop(state.windows.get_mut().remove(window_id)); | ||
| return Some(WindowEvent::Destroyed); | ||
| if self.with_state(|state| state.window_requests.get_mut().get(window_id).is_none()) { |
There was a problem hiding this comment.
Is there a reason why we call with_state several time?
I think this could be simplified maybe.
There was a problem hiding this comment.
decided to keep it as it is for now
| // If we have a popup the position is relative to the parent window and not | ||
| // relative to the screen. Therefore we have to translate it from the parent | ||
| // coordinate system to the display coordinate system | ||
| fn translate_outer_position(&self, position: Position) -> PhysicalPosition<i32> { |
There was a problem hiding this comment.
Looks like with_position(p) and a later set_outer_position(p) put the popup in two different places. The initial position needs the same translation.
Also outer_position() still returns screen coordinates, so the getter and setter now use different coordinate spaces. Probaly the getter needs to be translated too.
Or the documentation should be cristal clear about this difference. And we need to be somehow consistent across platforms if possible.
There was a problem hiding this comment.
The initial position for win32 is set using the set_outer_position function:
if let Some(position) = attributes.position {
win.set_outer_position(position);
}So that means the translate is done here. I will have a look into for the return value
There was a problem hiding this comment.
The outer_position returns now for windows and macOs the position relative to the parent if it is a popup
| let parent = match attributes.parent_window() { | ||
| Some(rwh_06::RawWindowHandle::Win32(handle)) => { | ||
| window_flags.set(WindowFlags::CHILD, true); | ||
| if !is_popup { |
There was a problem hiding this comment.
other platform return an error if there is no parents
Otherwise for multiple seats it could happen that we don't grab the keyboard
Implement proper decorationless popups by specifying the type of the child window with
with_type()With this PR different kind of child windows can be created
The type can be specified during creation of the Window using the window_attributes and the
with_type()function. As default a normal Window is used. IfPopupis choosen a parent must be specified, otherwise the Popup creation fails with an Error returned by thenew()function.Related issues: #403 and #4256
changelogmodule if knowledge of this change could be valuable to usersPlatforms
Wayland:
Bildschirmaufzeichnung.vom.2026-06-04.13-18-16.mp4
This work is sponsored by the NLnet foundation