Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autotype after a CHOICE causes an odd delay #5242

Open
2 tasks done
Dutchmagic opened this issue Oct 12, 2024 · 4 comments
Open
2 tasks done

Autotype after a CHOICE causes an odd delay #5242

Dutchmagic opened this issue Oct 12, 2024 · 4 comments
Labels

Comments

@Dutchmagic
Copy link

Describe the bug

Using a CHOICE option in the autoexec part of a .conf file followed by a autotype command, causes an odd delay within X.
It does continue after this delay.

Steps to reproduce the behaviour

This is just an easy example:

  1. Download the Explicit demo: https://files.scene.org/get/parties/1996/naid96/demo/hrn-expl.zip
  2. Use the conf file created for DosBox-X: https://github.com/joncampbell123/demotest/tree/master/unpacked/ftp.scene.org/mirrors/hornet/demos/1996/h/hrn-expl.zip
  3. Edit the autoexec section of the .conf file with:
    @choice /N /T:n,10 "Run hidden part? (Y or N)"
    IF ERRORLEVEL ==2 GOTO ORIG
    IF ERRORLEVEL ==1 GOTO HIDDEN

:ORIG
@autotype -w 0.5 enter enter enter enter y
@EXPLICIT.EXE
exit

:HIDDEN
@EXPLICIT.EXE -JA
exit

  1. Run the demo in DosBox and notice the odd delay when autotype is used (choosing N) and when it isn't (choosing Y).

Expected behavior

autotype should not cause a delay after using CHOICE.

What operating system(s) this bug have occurred on?

Windows 10 (but does not matter)

What version(s) of DOSBox-X have this bug?

Most current version

Used configuration

# This is the configuration file for DOSBox 0.800. (Please use the latest version of DOSBox)
# Lines starting with a # are comment lines and are ignored by DOSBox.
# They are used to (briefly) document the effect of each option.
[dosbox]
memsize=16

[cpu]
core=normal
cputype=pentium
cycles=25000

[dos]
umb=false

[gus]
gus=true

[speaker]
pcspeaker=true
initial frequency=0
disney=true

[sblaster]
sbtype=sbpro2

[autoexec]
@mount c .\hrn-expl
c:
cls
REM ------ RUN THE DEMO -------
@echo off
@CHOICE /N /T:n,10 "Run hidden part? (Y or N)"
IF ERRORLEVEL ==2 GOTO ORIG
IF ERRORLEVEL ==1 GOTO HIDDEN

:ORIG
@autotype -w 0.5 enter enter enter enter y
@EXPLICIT.EXE 
exit

:HIDDEN
@autotype -w 0.5 enter enter enter enter y
@EXPLICIT.EXE -JA
exit

Output log

No response

Additional information

No response

Have you checked that no similar bug report(s) exist?

  • I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

  • I agree to follow the code of conduct and the contributing guidelines.
@Dutchmagic Dutchmagic added the bug label Oct 12, 2024
@maron2000
Copy link
Contributor

As a workaround, you can insert a dummy line just before autotype command.

@choice /N /T:2,10 "Run hidden part? (Y or N)"
IF ERRORLEVEL ==2 GOTO ORIG
IF ERRORLEVEL ==1 GOTO HIDDEN

:ORIG
rem echo no
autotype -w 0.5 enter enter enter enter y
EXPLICIT.EXE
goto END

:HIDDEN
EXPLICIT.EXE -JA

:END

@Dutchmagic
Copy link
Author

Odd - an extra dummy line like that does not seem to help speed it up for me.

@maron2000
Copy link
Contributor

Okay, we still have to look in to this.

@Dutchmagic
Copy link
Author

The interesting thing is - the default choice (in the example choice N) will not cause a delay after the time-out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants