GNOME Bugzilla – Bug 797360
waylandsink: resize didn't support set window position
Last modified: 2018-11-03 14:37:16 UTC
when resize using videooverlay interface, the window position (x,y)didn't take effect for waylandsink. Do we have any software limitation.
It is a bit complicated due to the semantic of Wayland. Window don't really have a size, it's the surface we put in it the defines that. We should still try and match as much as possible the semantic found in xvimagesink. That might imply we need to add an extra, but fully transparent, sub-surface to ensure window size, otherwise it may look weird in gst-launch (when testing). The app you embed to, will have it's own surface we sub-surface. Clipping the right / bottom is likely the complicated bit due to Wayland.
(In reply to Nicolas Dufresne (ndufresne) from comment #1) > It is a bit complicated due to the semantic of Wayland. Window don't really > have a size, it's the surface we put in it the defines that. > > We should still try and match as much as possible the semantic found in > xvimagesink. That might imply we need to add an extra, but fully > transparent, sub-surface to ensure window size, otherwise it may look weird > in gst-launch (when testing). The app you embed to, will have it's own > surface we sub-surface. Clipping the right / bottom is likely the > complicated bit due to Wayland. I mean the whole surface left corner position not the subsurface position. E.g I want to place the whole surface at (100, 100) on the desktop. Is there anyway to do this? Currently, video will show at randomly position on the desktop
No, that is not possible with Wayland, you need to create a full screen surface first, and then you can place the video subsurface relatively to your surface. I started adding full screen shell support, maybe you could continue that work ?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/810.