XYplorer Beta Club

admin wrote: ↑26 Jun 2025 18:24 Not here

I started just now with a new ini file. At first it looked ok, but....

There was just one pane, line numbers were shown and in tools/customize list/"show line numbers" was checked.
I opened a second pane via F10, set focus on it, line numbers showed, opened tools/customize list/"show line numbers" and it was UNchecked. After i checked it the line numbers disappeared.

In the VB version it works correct.

Probably a focus issue. This is one area where TB still needs some adjustments.

New version of XYplorer (64-bit) compiled with twinBASIC BETA 820:

XYplorerTB.exe, v27.00.0805, 64-bit, NOT digitally signed, zipped
There will be glitches, there will be bugs. Work in progress.

XYTB is still XP+.

I hope further backward compatibility support will not become an obstacle to new features and SC, as it was with Autohotkey v1?

Hi Don! I have investigated this strange thing with toolbar buttons further and was finally able to spot the culprit and SOLVE it. It was/is about the toolbar buttons in general: When the Windows display scaling factor was/is defined as 175%, then, in the TB version, there is apparently a mismatch between the visible button size and its invisible "active area" (which is a bit wider!). That small mismatch sums up from left to right and so brings more and more "mess" to the toolbar (more to the right = more mess). The VB version does not have this issue at Windows display scaling factor of 175%. Both versions do not have this issue when the scaling factor is for instance 125%. Maybe this finding is relevant for the TB development.

TB .0805:
Command #642 (empty recycle bin) now works as expected from a custom toolbar button.

Hello just installed, without doing anything more here the screenshot
some problem with the display on the right side and below

MS Defender make an erronious assumption !!

MS Defender tags XY as a virus simply because once you have it you'll never get rid of it.

brianhuahin wrote: ↑28 Jun 2025 04:20 MS Defender make an erronious assumption !!

Who cares ?
It always makes this for new software.
Make an exception and go on.

Nice, entered registration info and it ran. Not yet tried with the original ini-file, are they compatible?

But very important question, how long will you continue to support W7, now that the likes of the Document Foundation and GIMP have decided to terminate support for it?

For what it's worth, one initial crash after restart and "Help->About->Close", but then stable. Worrying thing is of course, not for me, that you will never own TwinBasic, unless you're one of the people who secured a VIP perpetual licence.

Inline assembler will be useful if you want to make it even faster, but what do will they support? Bog-standard run-of-the-mill code, or, which is probably an order of magnitude harder, things like AVX, which I myself use, unsupported, in Virtual Pascal, and which really works wonders.

Win 11 up to date, XYplorerTB-27.00.0805
Using Synch Folders the Error message appears.

prino wrote: ↑28 Jun 2025 19:16 Nice, entered registration info and it ran. Not yet tried with the original ini-file, are they compatible?

But very important question, how long will you continue to support W7, now that the likes of the Document Foundation and GIMP have decided to terminate support for it?

For what it's worth, one initial crash after restart and "Help->About->Close", but then stable. Worrying thing is of course, not for me, that you will never own TwinBasic, unless you're one of the people who secured a VIP perpetual licence.

Inline assembler will be useful if you want to make it even faster, but what do will they support? Bog-standard run-of-the-mill code, or, which is probably an order of magnitude harder, things like AVX, which I myself use, unsupported, in Virtual Pascal, and which really works wonders.

It's currently fully compatible with the original INI file when reading it, but when writing it some 64-bit related keys are missing (in case you want to use this INI again with XYVB). But thinking about it, I will change this back to full two-way compatibility. I think it's useful for the VB->TB transition period.

Currently even XP support is still the Win version compatibility target. (With a few non-essential features excluded.) I don't see an end to W7 support for a long time.

"Help->About->Close": yes, crash after closing dialogs is a known issue. It will get eventually fixed, of course.

Why own? I worked so many years with a dead language I did not own. And I can stop upgrading TB whenever I want. There is no problem, only advantages.

Inline assembler: well, the bottle neck with a file manager is usually file I/O. And the TB version, once the compiler is optimized (which it currently isn't at all) will be much faster than the VB version anyway. So the need for inline assembler is small.

Borut wrote: ↑27 Jun 2025 21:53 Hi Don! I have investigated this strange thing with toolbar buttons further and was finally able to spot the culprit and SOLVE it. It was/is about the toolbar buttons in general: When the Windows display scaling factor was/is defined as 175%, then, in the TB version, there is apparently a mismatch between the visible button size and its invisible "active area" (which is a bit wider!). That small mismatch sums up from left to right and so brings more and more "mess" to the toolbar (more to the right = more mess). The VB version does not have this issue at Windows display scaling factor of 175%. Both versions do not have this issue when the scaling factor is for instance 125%. Maybe this finding is relevant for the TB development.

Yes, for some users Windows scaling breaks something, for others it doesn't. Bit of a mystery. I'm looking into it.

brianhuahin wrote: ↑29 Jun 2025 04:03 Win 11 up to date, XYplorerTB-27.00.0805
Using Synch Folders the Error message appears.

Cannot reproduce.