On Linux X11 I seem to be getting a ConfigEvent for each FrameEvent.
Is that the intended behavior?

-- Larry

On Fri, 19 Apr 2024 at 16:59, Larry Clapp <lclapp.gio@gmail.com> wrote:
>
> On Linux X11 I seem to be getting a ConfigEvent for each FrameEvent.
> Is that the intended behavior?
>

You get a ConfigEvent for every resize because Config.Size changes, but
otherwise no. I tested the kitchen example on X11 by enabling the progress
animation and verified that only FrameEvents were sent.

Do you have a case where you get both ConfigEvent and FrameEvent?

Elias

I may've been mistaken when I said "x11", because I get extra
ConfigEvents when I run kitchen with "go run ." but not with
"WAYLAND_DISPLAY=no go run ." So I guess it's a Wayland thing not an
X11 thing. I'm not resizing, the app is just sitting there.

-- L


On Sat, Apr 20, 2024 at 3:15 AM Elias Naur <mail@eliasnaur.com> wrote:
>
> On Fri, 19 Apr 2024 at 16:59, Larry Clapp <lclapp.gio@gmail.com> wrote:
> >
> > On Linux X11 I seem to be getting a ConfigEvent for each FrameEvent.
> > Is that the intended behavior?
> >
>
> You get a ConfigEvent for every resize because Config.Size changes, but
> otherwise no. I tested the kitchen example on X11 by enabling the progress
> animation and verified that only FrameEvents were sent.
>
> Do you have a case where you get both ConfigEvent and FrameEvent?
>
> Elias

On Sat, 20 Apr 2024 at 15:56, Larry Clapp <lclapp.gio@gmail.com> wrote:
>
> I may've been mistaken when I said "x11", because I get extra
> ConfigEvents when I run kitchen with "go run ." but not with
> "WAYLAND_DISPLAY=no go run ." So I guess it's a Wayland thing not an
> X11 thing. I'm not resizing, the app is just sitting there.
>

I did test Wayland, but didn't realize the issue only occurred with client
side decorations which are not enabled on Sway.

The issue should be fixed in the latest Gio.

Thanks,
Elias