XYplorer Beta Club

Marc wrote: ↑08 Jul 2025 16:55 PS.
I think it would be a good idea to add x64 after the version number in the title bar as long as the VB x86 version still exists (for those who use both versions as long as the x64 version is not finished).

You can do this in settings - templates using the variable <xybitness>.

christian777 wrote: ↑08 Jul 2025 17:20

Marc wrote: ↑08 Jul 2025 16:55 PS.
I think it would be a good idea to add x64 after the version number in the title bar as long as the VB x86 version still exists (for those who use both versions as long as the x64 version is not finished).

You can do this in settings - templates using the variable <xybitness>.

mumajs wrote: ↑08 Jul 2025 13:07 However I dont know if that was already discussed, even I change drive in left pane or right pane it change drive in active pane. I have C: drive in left active pane, but when I click to change drive in right pane it does not change the drive in right pane and get focus but it change the drive in left active pane.

Either I can't reproduce it or I didn't understand it.

Marc wrote: ↑08 Jul 2025 16:55 Check for update does not work if language selected is french but is OK if back to english.
in french language XY doesn't even open the Internet connection (whatever beta with Ctrl or not)

Can't confirm. Works fine here with French.

admin wrote: ↑07 Jul 2025 15:52...I think the 64-bit version will officially be released by the end of July 2025...

It's an exciting time, yesterday I renamed my directories so that I'm using the TwinBasic release by default.

Apart from a couple hiccups with the preview window and base64encode, it all feels like it's coming together. Those inline rename issues from the first release feel like a lifetime ago.

I'm looking forward to full unicode support, that way I can start throwing in a every time I call echo

What's that about base64encode?

Yesterday, when I tried to use it on a file, I got an invalid parameter error. The same line worked fine in the VB edition.

I'm not home right now to provide the code, but I believe it was a basic copytext base64encode(,"<selitem>")

Yeah, doesn't work with TB, neither with strings nor files

Fixed in next beta. (Took me half of the day )

SC: In one of my scripts I have apparently been using (for what it is worth) the undocumented command sendkeys, like this:When used from the address line, alone, apparently nothing happens. When used in the original script (immediately after a focus;), there is some short message appearing on screen for a split second (kind of a separate small info form, but could not see what it says). Some 2-3 seconds later XY silently dies. This does not happen in the VB version.

Any ideas? Is it better to simply avoid the undocumented sendkeys? (Basically wanted simply to document this finding.)

Borut wrote: ↑10 Jul 2025 16:17Is it better to simply avoid the undocumented sendkeys?

Undocumented, but it is widely used.

A simple script like: with the latest TB beta and a filled LFB doesn't lead to anything but the expected result: a cleared LFB...

admin wrote: ↑09 Jul 2025 09:17

mumajs wrote: ↑08 Jul 2025 13:07 However I dont know if that was already discussed, even I change drive in left pane or right pane it change drive in active pane. I have C: drive in left active pane, but when I click to change drive in right pane it does not change the drive in right pane and get focus but it change the drive in left active pane.

Either I can't reproduce it or I didn't understand it.

Sorry for late answer, however the issue is solved in the latest x64 beta

highend wrote: ↑10 Jul 2025 16:56A simple script like:

Code: Select all

    focus "LFB";
    sendkeys "{Esc}";

with the latest TB beta and a filled LFB doesn't lead to anything but the expected result: a cleared LFB...

Thanks for checking highend! Yes, I agree: In my case the issue is sometimes not happening, but mostly it does. I could not recognize any system in it. Meanwhile I have been recording the screen and have found out that, when it happens, what appears briefly is a yes/no dialog from Windows (sic!), entitled - in my case in German - "Hiermit werden alle anstehenden Übertragungen abgebrochen.", containing the question "Sind Sie sicher, dass Sie alle Übertragungen abbrechen möchten?". Complete bullshit, as it seems. A few possibly relevant pages that I was able to found about such a message did not help. However, my current workaround is to use #675; #675; instead. In that way the same intended task seems to be achieved, while the issue apparently never appears.

If you are just trying to remove a active LF, I think I'd recommend this way instead filter , 8;

@Don: I noticed something a little strange in x64, cmd seems not to inherit its enviro vars, eg goto "!set";