x64: SC confirm buttons malfunctioning

Things you’d like to miss in the future...
Forum rules
:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:

:info: Please include the following information:
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).

:info: We strongly recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once, and we won't have to search for that vital information.

:info: When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".

:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:
Post Reply
jupe
Posts: 3541
Joined: 20 Oct 2017 21:14
Location: Win10 22H2 120dpi

x64: SC confirm buttons malfunctioning

Post by jupe »

I have been having issues with SC confirm since recent Glow Up changes, eventually I managed to make a repro below for fresh.

If you run it and press YES in first confirm, then OK in echo, you'll notice that in the second confirm YES button appears non functional if you try and press it, but it actually is functional it just performs as a Copy button (from the echo dialog) instead, so you can't press YES in the second confirm or any subsequent ones for the rest of the session, instead it acts as a Copy button.

Code: Select all

e confirm("Press YES in this dialog, then OK in Echo", , , 3); confirm("If you try press YES in this dialog, this dialogs text is copied instead", , , 3);
Once this issue is triggered it basically requires a restart to resolve, since as yet I haven't been able to find a workaround besides script modification.

admin
Site Admin
Posts: 67059
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: x64: SC confirm buttons malfunctioning

Post by admin »

Confirmed & fixed in next beta. :tup:

Post Reply