Hi,
Thank you for the input.
id-agent plugin is not in use at present. This particular system has 2
classes of applications.
1. Qt applications - They use IVI_SURFACE_ID environment variable to set
the surface ID for each application via an init shellscript.
2. XOrg applications - These are running with help from xwayland and the
surface IDs for these is at provided via weston.ini.
So I should use id-agent for XOrg applications to set surface ID instead of
providing via weston.ini. And so we will get control of surface ID's when
using multiple instances. I think this could be a valid solution. I'll try
to figure this out.
Meanwhile the multi-instance use case is thrown out for now, so for single
instance of the XOrg application, providing a fixed surface ID via
weston.ini works fine for now.
Regards,
Vaibhav
On Wed, Jun 16, 2021 at 1:53 AM Eugen Friedrich wrote:
> Hi Dalvi,
>
> The ivi id is something application needs to set explicitly, need to
> understand how the id is assigned for application you already can control?!
> Are you using id-agent plugin?
>
> Best regards
> Jena
>
> Vaibhav Dalvi schrieb am Fr. 4. Juni 2021 um
> 07:19:
>
>> Hi all,
>> I'm working on a simple C++ application (dbus-service) which can
>> start/stop another application ( a vnc viewer application ). My platform is
>> arm-linux with wayland + ivi-shell. Now I am able to start / stop the x11
>> vncviewer application one instance. Needed to add desktop-app entries in
>> weston.ini. I'm using LayerManagerControl commands to manage the window (
>> at present - further on ilm API's shall be used. )
>>
>> Now my next use case is multiple instances of this vnc viewer
>> application. And for that I added few more desktop-app entries to
>> weston.ini, and updated the service to launch multiple instances of vnc
>> viewer. I am able to launch multiple instances of vncviewer. But to control
>> those instances, I need to know which instance is assigned which surface
>> ID.
>>
>> Another look at ilm api's led me to surface-property's creator-PID field.
>> Unfortunately with xwayland, for x11 apps this field contains PID of
>> xwayland instance and not the actual x11 app.
>>
>> I looked at libweston as well as xwayland-api, but not able to see a
>> clear solution. Please suggest any way to obtain this mapping of surface ID
>> and process ID for x11 apps with xwayland.
>>
>> ___
>> wayland-devel mailing list
>> wayland-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/wayland-devel
>>
>
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
