On Sun, 3 Sep 2023 15:33:33 GMT, Thiago Milczarek Sayao
wrote:
>> The bug happens because `gdk_window_get_frame_extents` is not returning the
>> correct position when o i3-wm, probably by some bug on the wm itself.
>>
>> Te fix replaces the usage of the function for already known extents value
On Sun, 9 Jul 2023 17:43:05 GMT, Thiago Milczarek Sayao
wrote:
> The bug happens because `gdk_window_get_frame_extents` is not returning the
> correct position when o i3-wm, probably by some bug on the wm itself.
>
> Te fix replaces the usage of the function for already known extents value
>
On Sun, 9 Jul 2023 17:43:05 GMT, Thiago Milczarek Sayao
wrote:
> The bug happens because `gdk_window_get_frame_extents` is not returning the
> correct position when o i3-wm, probably by some bug on the wm itself.
>
> Te fix replaces the usage of the function for already known extents value
>
On Mon, 10 Jul 2023 08:06:34 GMT, Johan Vos wrote:
>> The bug happens because `gdk_window_get_frame_extents` is not returning the
>> correct position when o i3-wm, probably by some bug on the wm itself.
>>
>> Te fix replaces the usage of the function for already known extents value
>> calculat
On Sun, 9 Jul 2023 17:43:05 GMT, Thiago Milczarek Sayao
wrote:
> The bug happens because `gdk_window_get_frame_extents` is not returning the
> correct position when o i3-wm, probably by some bug on the wm itself.
>
> Te fix replaces the usage of the function for already known extents value
>
On Sun, 9 Jul 2023 17:43:05 GMT, Thiago Milczarek Sayao
wrote:
> The bug happens because `gdk_window_get_frame_extents` is not returning the
> correct position when o i3-wm, probably by some bug on the wm itself.
>
> Te fix replaces the usage of the function for already known extents value
>