On Thu, Jul 13, 2017 at 1:49 PM, Marco Martin wrote:
> On Thu, Jul 13, 2017 at 11:05 AM, David Edmundson
> wrote:
>> That works fine for XDG, but wl-shellsurface doesn't like that and remains
>> until you delete the wl_surface. wl_shell_surface_destroy literally sends
>> nothing in wayland_debug.
On Thu, Jul 13, 2017 at 11:05 AM, David Edmundson
wrote:
> That works fine for XDG, but wl-shellsurface doesn't like that and remains
> until you delete the wl_surface. wl_shell_surface_destroy literally sends
> nothing in wayland_debug.
>
> I think that's why they end up deleting both. It's not a
>IIRC wl_shell is not defined to be double buffered. Not sure how it's
about xdg. There is always the chance of breaking things *cough*Qt*cough*
when changing that - even if it is sane.
Xdg definitely is and for v7 this is important as mapping/unmapping is
different.
* committing a surface with e
On Thursday 13 July 2017 09:56:38 you wrote:
> with a qt more recent than https://codereview.qt-project.org/#/c/195835/
> surfacecreated events may be again sent at the right moments?
> (tough reverting https://bugreports.qt.io/browse/QTBUG-58423 would still be
> a good thing)
another good thing c
On Thursday 13 July 2017 09:56:38 you wrote:
> with a qt more recent than https://codereview.qt-project.org/#/c/195835/
> surfacecreated events may be again sent at the right moments?
> (tough reverting https://bugreports.qt.io/browse/QTBUG-58423 would still be
> a good thing)
maybe let's try a Qt
On Wednesday 12 July 2017 20:51:16 Martin Flöser wrote:
>
> You might be right. Given the output of KWin debug console all the calls
> didn't work.
>
> THIS SUCKS! So show event is too early and expose event is too late. God
> damn Qt why did you have to break this??? We had working code and now
Am 2017-07-12 19:02, schrieb Marco Martin:
On Wednesday 12 July 2017 18:45:54 Martin Flöser wrote:
> Any ideas or advice?
So played with the KRunner code, resulted in:
https://phabricator.kde.org/D6654
Summary, don't use expose event, use show event
uh, this means we have to get the rest on
On Wednesday 12 July 2017 18:45:54 Martin Flöser wrote:
> > Any ideas or advice?
>
> So played with the KRunner code, resulted in:
> https://phabricator.kde.org/D6654
>
> Summary, don't use expose event, use show event
uh, this means we have to get the rest on showevent as well then?
i tought th
Am 2017-07-12 18:35, schrieb David Edmundson:
On Wed, Jul 12, 2017 at 4:02 PM, Martin Flöser
wrote:
Hi all,
I had a look at the issues of KRunner on Wayland with Qt 5.9 and
want to share my findings.
What we see is KRunner working fine on first invokation, but
afterwards everything is messed
Am 2017-07-12 17:02, schrieb Martin Flöser:
Hi all,
I had a look at the issues of KRunner on Wayland with Qt 5.9 and want
to share my findings.
What we see is KRunner working fine on first invokation, but
afterwards everything is messed up:
* maximized windows shortly change their size
* KRunne
On Wed, Jul 12, 2017 at 4:02 PM, Martin Flöser wrote:
> Hi all,
>
> I had a look at the issues of KRunner on Wayland with Qt 5.9 and want to
> share my findings.
>
> What we see is KRunner working fine on first invokation, but afterwards
> everything is messed up:
> * maximized windows shortly ch
Hi all,
I had a look at the issues of KRunner on Wayland with Qt 5.9 and want to
share my findings.
What we see is KRunner working fine on first invokation, but afterwards
everything is messed up:
* maximized windows shortly change their size
* KRunner opens behind other windows
With WAYLAN
12 matches
Mail list logo
