x64: SC inputselect header is persistent

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: 3327
Joined: 20 Oct 2017 21:14
Location: Win10 22H2 120dpi

x64: SC inputselect header is persistent

Post by jupe »

I noticed that in x64 the SC inputselect header param seems to persist during the session, ie if you run this in fresh:

inputselect("HEADER", 4:=1); inputselect("header 2");

you will only see the capitalized first header, even after script ends on subsequent runs during the session. And if your first use of inputselect doesn't use the header param, it seems the header section doesn't show at all for the rest of the session.

Currently using, .0507 but it was the same in earlier beta releases.

klownboy
Posts: 4446
Joined: 28 Feb 2012 19:27
Location: Windows 11, 25H2 Build 26200.7462 at 100% 2560x1440

Re: x64: SC inputselect header is persistent

Post by klownboy »

Thank you jupe, that explains why I was seeing a "Sort" header when I was using the "Delete" mini tree menu item. If I first sorted the mini trees and then used the delete mini menu item, I saw the header for the sorting. I just checked using v28.10.0507 and the issue still exists. I didn't explain how to properly recreate the problem when I reported it to highend (i.e., using sort first), but it is still a problem. viewtopic.php?p=235659#p235659

Post Reply