bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: GNUbg development build - BUG Report: Can't change options without m


From: Ian Shaw
Subject: RE: GNUbg development build - BUG Report: Can't change options without moving window
Date: Thu, 10 Aug 2023 10:27:42 +0000

Hi Philippe, 

I hadn't used gnubg for a while on this PC. I just installed version 1.08 so 
that I could try the new features.

I've found these versions still on the system. They have the same problem. 
GNU Backgammon 1.07.001-mingw 32-Bit 20221114
GNU Backgammon 1.06.002-mingw 32-Bit 20220703

I hadn't noticed the problem before I reported it, but of course I don't change 
settings regularly. 

Regards,
Ian

-----Original Message-----
From: Philippe Michel <philippe.michel7@free.fr> 
Sent: Thursday, August 10, 2023 9:36 AM
To: Ian Shaw <Ian.Shaw@riverauto.co.uk>
Cc: bug-gnubg@gnu.org
Subject: Re: GNUbg development build - BUG Report: Can't change options without 
moving window

On Tue, Aug 08, 2023 at 09:07:07AM +0000, Ian Shaw wrote:
> 
> 
> After changing an option, the window becomes unresponsive until I 
> reposition it by dragging the title bar.
[..]
> GNU Backgammon 1.08.dev-mingw 32-Bit 20230709
> 
> 64-bit Windows 10 Pro Version 22H2 OS build 19045.3271 Windows Feature 
> Experience Pack 1000.19041.1000.0

I can't reproduce the issue on the closest Windows version I have access to 
which is build 19045.3208

Possibly relevant is this paragraph in the notes from the KB raising the build 
to .3271:

The latest update focuses on resolving a specific concern related to Event 
Forwarding Subscriptions. When you include an Event Channel in the 
subscription, it will no longer forward events that are unnecessary or 
irrelevant to your needs. This enhancement ensures a more streamlined and 
efficient event forwarding process, saving valuable resources and improving the 
overall system performance.

Ian, did you install this version of gnubg when your machine was already at 
.3271 ? If not, did it work before and started to behave as you describe after 
the Windows update ?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]