WBAT misbehaving when calling batch file

[QmwJlHuSg9pa]

Are you using the latest Dosbox-Staging Version?

• I have checked releases and am using the latest release.

Different version than latest?

No response

What Operating System are you using?

Linux x86_64

If Other OS, please describe

No response

Relevant hardware info

AMD Ryzen 2600X, AMD RX 580

Have you checked that no other similar issue already exists?

• I have searched and not found similar issues.

A clear and concise description of what the bug is.

WBAT is a utility that renders bespoke graphical interfaces. I have been using it to generate configuration dialog menus for games, though have noticed some of its core behaviour has broken after updating to v0.81.

Here's an example regarding the included demo script "colors.bat":

• Expected output (as per v0.80.1):

  Selecting a colour with the corresponding keyboard shortcut results in an immediate update to the example graphic.

  
  After pressing "u":
  

• Actual output (v0.81.0, v0.81.1):

  Colour selection appears delayed by an entire round -- a second keyboard shortcut must be pressed before the first selection is reflected by the graphic. This delay seems common to any variables set through "call w.bat".

Steps to reproduce the behaviour.

1. Download WBAT v2.50 (wbat250.zip, "Dialog boxes for DOS batch") — https://www.horstmuc.de/ui.htm

2. Extract "wbat250" directory to drives/u/

3. Run dosbox-staging, enter commands:

   u:
   cd wbat250
   colors.bat
   

Download URL of affected game or software

https://www.horstmuc.de/ui.htm

Your configuration

Default config.

Provide a Log

No response

Code of Conduct & Contributing Guidelines

• Yes, I agree.

[weirddan455]

I can reproduce this on 0.81.1 but it appears to have been fixed on main (not sure by what commit exactly).

[johnnovak]

@QmwJlHuSg9pa Can you confirm this works now as expected with the latest dev build?

[QmwJlHuSg9pa]

@QmwJlHuSg9pa Can you confirm this works now as expected with the latest dev build?

Yes, can confirm this appears fixed in 0.82.0-alpha (7516d). Thank you both.

[johnnovak]

@QmwJlHuSg9pa Can you confirm this works now as expected with the latest dev build?

Yes, can confirm this appears fixed in 0.82.0-alpha (7516d). Thank you both.

Thanks @QmwJlHuSg9pa. Closing.