your library is using the same wl_display
instance as the application. If they don't, they become two separate
Wayland clients, which is effectively the same as separate processes.
Btw. "foreign surface" is usually used to refer to cross-process
references to Wayland surface, e.g. by usin
On Thu, Nov 26, 2020 at 02:53:05PM -0500, gherissi ayachi wrote:
> Hi,
>
> Background: our library allow to grab video to a supplied windows handle,
> When using X11 the user pass the XID to the lib
>
> and we can paint to this Window and do some interaction (pointer), All is
> done in the same p
Hi,
Background: our library allow to grab video to a supplied windows
handle, When using X11 the user pass the XID to the lib
and we can paint to this Window and do some interaction (pointer), All
is done in the same process.
In Wayland, The user has to provide us with his wl_display and
w
On 10 July 2018 6:03:26 pm AEST, David Edmundson
wrote:
>>Hm. If you wanted to, you could make this explicit by requiring an
>event serial in the export_surface request rather than the wl_surface.
>
>Certainly an option. Though I'm not sure we have a use case of needing
>to limit a client releasi
>Hm. If you wanted to, you could make this explicit by requiring an event
>serial in the export_surface request rather than the wl_surface.
Certainly an option. Though I'm not sure we have a use case of needing
to limit a client releasing its focus?
>Does this interface need to exist?
It doesn'
On Fri, Jul 6, 2018 at 1:26 AM, David Edmundson
wrote:
This protocol is to address the following use case.
A user clicks on a URL link in an IRC chat and a web browser opens.
We want an existing browser window to raise or if it's a newly
spawned application to claim focus on startup.
Nat
On Thu, Jul 5, 2018 at 4:56 PM, Drew DeVault wrote:
> I'm not sure why an activiation request has to jump through these
> surface export hoops first.
>
I think it's important to distinguish focus/raising from urgent/needs
attention hints.
I'm only interested in focus/raising.
Historically on X
On 2018/7月/05 04:26, David Edmundson wrote:
> This protocol is to address the following use case.
>
> A user clicks on a URL link in an IRC chat and a web browser opens. We want
> an existing browser window to raise or if it's a newly spawned application
> to claim focus on startup.
>
> Naturally
I'm not sure why an activiation request has to jump through these
surface export hoops first. We export a surface... to do what with it?
Export it to whom? What do they do with it? Instead, we could just
activate the surface (though I'd suggest activating an xdg_toplevel
rather than an arbitrary su
This protocol is to address the following use case.
A user clicks on a URL link in an IRC chat and a web browser opens. We want
an existing browser window to raise or if it's a newly spawned application
to claim focus on startup.
Naturally we also don't want any arbitrary client to be able to rai
On Sat, Mar 23, 2013 at 2:15 AM, Bill Spitzak wrote:
> Jonas Ådahl wrote:
>
>> There are two clients (A and B) that can communicate via some IPC
>> mechanism where A is the main process and B is a render process. B
>> renders to a surface and A decides its visibility and position. Below
>> follows
ll would need to synchronize frames with each other so that no
frame will have size mismatches.
>
> On Fri, Mar 22, 2013 at 2:49 AM, Jonas Ådahl wrote:
>> A foreign surface is a surface created given a handle associated with a
>> previously exported surface. A handle is a randomly gen
Jonas Ådahl wrote:
There are two clients (A and B) that can communicate via some IPC
mechanism where A is the main process and B is a render process. B
renders to a surface and A decides its visibility and position. Below
follows an example how foreign surfaces can be used.
1. Both A and B conn
Also, there's a potential treading issue: see below
On Fri, Mar 22, 2013 at 2:49 AM, Jonas Ådahl wrote:
> A foreign surface is a surface created given a handle associated with a
> previously exported surface. A handle is a randomly generated unique
> identifier that on the ser
A foreign surface is a surface created given a handle associated with a
previously exported surface. A handle is a randomly generated unique
identifier that on the server can associate a handle with a surface.
The exported surface is a surface created as normal but exported via the
15 matches
Mail list logo
