Update:
1. Weston has WIP patch to enable force-on option for output.
This makes output always connected and Qt apps works with this option.
However when I started weston without screen connected I encountered
a crash from intel i915 driver with intel_dp_compute_config on top
of
On 19 June 2018 at 18:49, Tomasz Olszak wrote:
> It needs OpenGL and 60fps from camera.
>
> Anyway I got some hints from QtWayland maintainer and hopefully small patch
> will allow me to use wayland without screen and show application on real
> screen once it is available.
>
> Will let you know
It needs OpenGL and 60fps from camera.
Anyway I got some hints from QtWayland maintainer and hopefully small patch
will allow me to use wayland without screen and show application on real
screen once it is available.
Will let you know once I finish and test it.
2018-06-19 3:39 GMT+02:00
On 18 June 2018 at 23:26, Tomasz Olszak wrote:
> Hello,
>
> Has anyone of you needed to handle following use case?
>
>
> 1. Linux
> 2. Full screen GUI app - fast as much as possible so no X, considered eglfs
> over drm and wayland
> 3. It starts as a service without screen
> 4. Screen can be
@Francisco
Perhaps it wold be possible to move non GUI code out from application and
create gui one connecting with backend.
@Tony
Sorry using word "service" was unfortunate. The app is just started from
systemd - that's all. It is GUI application using OpenGL, Qt Quick etc.
I noticed that it
Hi Tomasz,
I think in Windows, it simply is not possible for a service app to also
run in desktop - they have separate desktops. The usual solution is to
move data and commands between the service and desktop app via some form
of inter process communication - TCP, pipes, mailslots, etc.
Hello,
Has anyone of you needed to handle following use case?
1. Linux
2. Full screen GUI app - fast as much as possible so no X, considered
eglfs over drm and wayland
3. It starts as a service without screen
4. Screen can be connected at any time - app should be visible on screen
3 seems
