From 44b77a26e8cb29252d7767735b4a38abd24976bf Mon Sep 17 00:00:00 2001
From: Dmitry Karasik <dmitry@karasik.eu.org>
Date: Wed, 25 Oct 2023 21:59:10 +0200
Subject: [PATCH] refs #100: fixes for fvwm

as we're testing virtual size, not real size, the specificities
of WMs, namely how much they delay ConfigureNotify and how Prima
deals with it, is not really the point of this test.

Here, fvwm2 indeed delays these events and they come long after the last
restore() call, but it's not wrong in a sense that Prima cannot wait for
these forever; if a WM is slow, then it's slow.
---
 t/Widget/Size.t | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/t/Widget/Size.t b/t/Widget/Size.t
index a34a53c24..84456b665 100644
--- a/t/Widget/Size.t
+++ b/t/Widget/Size.t
@@ -43,9 +43,11 @@ $window-> size( 200, 200);
 @w = $window-> get_virtual_size;
 $window-> restore;
 is_deeply( \@w, [200,200], "in maximized state" );
+$window->destroy;
 
 ####################################
 
+$window = create_window;
 my @sz1 = $window-> size;
 my $ww = $window-> insert( Widget =>
                            size => [ -2, -2],