XYplorer Beta Club
Ctrl+G
e "<crlf>";I assume it should operate like the AB instead.
Go To... dialog resolving variables early
Forum rules
READ THIS AND DO IT!!!
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%).
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.
When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".
READ THIS AND DO IT!!!
READ THIS AND DO IT!!! 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%).
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. When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files". READ THIS AND DO IT!!!
-
jupe
- Posts: 3462
- Joined: 20 Oct 2017 21:14
- Location: Win10 22H2 120dpi
Go To... dialog resolving variables early
I noticed that for scripts, the Go To.. dialog resolves <crlf> variables first, then runs the input, it probably happens for all variables, but those may not generate an issue as readily as this. eg.
Ctrl+G
I assume it should operate like the AB instead.
Ctrl+G
I assume it should operate like the AB instead.
-
admin
- Site Admin
- Posts: 66560
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
