XYplorer Beta Club

Okay, I saw a way to reproduce this. Will be fixed in the next release.

So to use the button you have to have RAF shown/enabled in the tree, is that correct?

PS: Recently something seems to have gone wrong with SC raf, it is resolving VFO variables on entry when they have labels, eg goto <xypath>; raf('PICK>vi:<pick>', s); topindex(t, t);

Some facts relative to MY configuration :
XY version 26.90.0000
Started as admin, Help/Environment variables shows » %rapidaccess% = rapid access
Started as non-admin » %rapidaccess% = (empty)

When in Rapid access folder root, typing in the address bar results in the following error message :
When outside the Rapid access folder tree, nothing happens, nothing.

It works in a fresh instance and some others, so I guess it's something to do with some particular settings.
Any idea ?

jupe wrote: ↑17 Feb 2025 06:23 So to use the button you have to have RAF shown/enabled in the tree, is that correct?

Using the button with RAF disabled in the tree will be less jerky in the next beta.

jupe wrote: ↑17 Feb 2025 06:23 PS: Recently something seems to have gone wrong with SC raf, it is resolving VFO variables on entry when they have labels, eg goto <xypath>; raf('PICK>vi:<pick>', s); topindex(t, t);

Confirmed. Fix comes.

Daniel0312 wrote: ↑17 Feb 2025 09:00 Some facts relative to MY configuration :
XY version 26.90.0000
Started as admin, Help/Environment variables shows » %rapidaccess% = rapid access
Started as non-admin » %rapidaccess% = (empty)

Are you using Environment variables in your Startup.ini or Admin.ini?

no startup.ini file, and admin.in only have license info

Could you send your XYplorer.ini to support?

Thanks, got it. However, I could not reproduce the issue.

I checked again and I may have misled you.
The command line parameters are the following /ini=XYdata\%COMPUTERNAME%\%COMPUTERNAME% /script=Init_Perm
When I replace %COMPUTERNAME% by it's resolved value, the Environment variable %rapidaccess% is initialized and everything works as expected.

Yeah, that helped. Should be fixed in next beta.

fixed in 26.90.0002
thanks