On Monday 17 February 2014 16:36:45 Martin Gräßlin wrote:
> No that doesn't work as I expect that at least during the next decade we
> will have both WAYLAND_DISPLAY and DISPLAY being set (DISPLAY for legacy
> applications which won't have a Wayland port any time soon - e.g. Qt4).
Then I don't se
On Monday 17 February 2014 23:30:07 Christoph Cullmann wrote:
> - Ursprüngliche Mail -
>
> > > > wrapper.cpp assumes there is a DISPLAY env variable and even if not
> > > > it's
> > > > set to ":0".
> > >
> > > Can't we detect that we're not on X11 simply from the fact that DISPLAY
> > >
- Ursprüngliche Mail -
> > > wrapper.cpp assumes there is a DISPLAY env variable and even if not it's
> > > set to ":0".
> >
> > Can't we detect that we're not on X11 simply from the fact that DISPLAY is
> > not set?
>
> No that doesn't work as I expect that at least during the next decad
On Saturday 15 February 2014 20:49:39 David Faure wrote:
> On Thursday 13 February 2014 09:29:40 Martin Gräßlin wrote:
> > Hi,
> >
> > on my quest to ensure that we can run all applications with -platform
> > wayland if compiled with X11 support I stumbled over
> > kinit/kdeinit/kinit.cpp which ge
On Thursday 13 February 2014 09:29:40 Martin Gräßlin wrote:
> Hi,
>
> on my quest to ensure that we can run all applications with -platform
> wayland if compiled with X11 support I stumbled over
> kinit/kdeinit/kinit.cpp which gets compiled into the kdeinit5 binary. To
> quote the code:
>
> // Ca
Hi,
on my quest to ensure that we can run all applications with -platform wayland
if compiled with X11 support I stumbled over kinit/kdeinit/kinit.cpp which
gets compiled into the kdeinit5 binary. To quote the code:
// Can't use QGuiApplication::platformName() here, there is no app instance
An
