re: bin/58467: ctwm does not move the application window to the specified workspace

["RVP via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR bin/58467; it has been noted by GNATS.

From: RVP <rvp%SDF.ORG@localhost>
To: matthew green <mrg%eterna23.net@localhost>
Cc: gnats-bugs%netbsd.org@localhost
Subject: re: bin/58467: ctwm does not move the application window to the
 specified workspace
Date: Sun, 12 Jan 2025 09:28:31 +0000 (UTC)

 On Sun, 12 Jan 2025, matthew green wrote:
 
 > can you explain what the change does?  ie, why does having these
 > as 0 ever cause a problem?  i'm just trying to understand what's
 > wrong and why this fixes it, thanks.
 >
 
 I had a quick look when this bug was originally filed. What's happening when
 both values are 0 (not otherwise) is that in event_handlers.c:HandleExpose()
 line 1667, the Event.xany.window is _never_ the main window itself, so and the
 optimization fails to paint the Occupy window. The HandleExpose _is_ called
 for all the other 5 WS buttons. and the 3 action buttons, however.
 
 You can remove that check, and then it works with the 0 values, but, then the
 Occupy window gets painted 9 times (with the std. config.: 1 + 5 + 3 times).
 
 Didn't chase this any further.
 
 HTH,
 
 -RVP