XYplorer Beta Club

Here's my next shot: viewtopic.php?p=220787#p220787

I tested v25.90.0154 and it does the same thing as v25.90.0152. The context menu still tries to use the overlong paths instead of 8.3 short names.

I also have the Long Paths setting enabled on my Windows 10.

Strange, it worked on my long path enabled Windows 10. Or are you using the 64-bit context menu?

No, I am using the standard context menu. For testing, I use a fresh instance of XYplorer and default settings. Scripting > Run Script > Fresh

I've been testing overlong video files with VLC Player. Are you testing with the same program?

I have now tested it with VLC Player on long path aware Win10 and can confirm what you see. The DOS 8.3 is correctly passed to the shell context menu, and then Windows takes over and apparently (black box) converts that path back to a long path internally before passing it to VLC. Nothing I can do about that.

PS: Does it work via context menu when you open it in File Explorer?

admin wrote: ↑18 May 2024 18:49 PS: Does it work via context menu when you open it in File Explorer?

Yes.

admin wrote: ↑18 May 2024 09:32 The DOS 8.3 is correctly passed to the shell context menu, and then Windows takes over and apparently (black box) converts that path back to a long path internally before passing it to VLC. Nothing I can do about that.

Interesting... I think I found a solution!

In the XYplorer app manifest, there is a "longPathAware" flag since v24.80. It seems this setting causes Windows to convert the 8.3 paths from XYplorer back into overlong paths, breaking some apps.

I removed the "longPathAware" flag by editing the manifest file with an app called Resource Hacker, and now the XYplorer context menu successfully opens overlong files!

Please try removing this flag from the manifest, and recompiling XYplorer. Overlong paths are working perfectly for me now!

 

Wow, good find! I'll check that.

Note that longPathAware was added to the manifest in v24.80.0020 - 2023-08-21 17:46. Probably this alone was/is responsible for the opening problems you were/are having? (You can check by testing an older version from the freezer: https://www.xyplorer.com/freezer.php)

Note that longPathAware in the manifest also has good effects: E.g. you get a shell context menu for overlong items.

The real problem here is the VLC application, not XYplorer. They're the ones that should handle long paths properly.

This might not be related, but since around version 25.90.0148 onwards XY has been misbehaving when it comes to passing arguments that contain spaces to commands.

I have a number of bash scripts that I run from XY. These bash scripts take the selected entries from the list view as arguments.

For example I have a folder called "Test folder one".
If I select this folder in the LV and run one of my bash scripts, under XY 25.90.0147 the script receives a single argument "D:\Users\John\Documents\Test folder one".
If I run the same under XY 25.90.0155, the script receives three arguments "D:\Users\John\Documents\Test", "folder" and "one".

Cheers
John

Ah, thanks for the hint. Should work again next beta.

admin wrote: ↑18 May 2024 23:08 Note that longPathAware was added to the manifest in v24.80.0020 - 2023-08-21 17:46. Probably this alone was/is responsible for the opening problems you were/are having? (You can check by testing an older version from the freezer: https://www.xyplorer.com/freezer.php)

v24.60: overlong paths work perfectly -- because XYplorer opens them using 8.3 short names

v24.80: overlong paths start to break -- because of longPathAware, XYplorer now opens the *huge* overlong paths directly, breaking many apps with the "MAX_PATH" limit of 260 characters.

v25.90.0154 beta: double clicking overlong files was fixed and now uses 8.3 names -- BUT the context menu still uses overlong names because of longPathAware (forced conversion of 8.3 names to overlong on the shell)

Ironically, it seems the "longPathAware" flag tells Windows to no longer use 8.3 short names when opening overlong files in XYplorer. But this breaks many programs!

admin wrote: ↑18 May 2024 23:08 Note that longPathAware in the manifest also has good effects: E.g. you get a shell context menu for overlong items.

When I disable longPathAware in the newest beta version, the context menu now works perfectly for overlong items. It actually *FIXES* the issues with VLC Player, Notepad++, context menu, shell extensions, and other programs.

It's a weird quirk in Windows! Please try disabling longPathAware and opening overlong files (both in the context menu + also double clicking). It solves all my issues.

Ah, thanks for the hint. Should work again next beta.

Fixed now thanks

Julia1995 wrote: ↑19 May 2024 21:56 Please try disabling longPathAware and opening overlong files (both in the context menu + also double clicking). It solves all my issues.

As I said, longPathAware also has its advantages, and I have at least one app, that *only* can open overlong files when longPathAware is in the manifest. It cannot handle 8.3 paths. And it's likely that less and less apps can handle 8.3 paths. longPathAware is the future, 8.3 paths is just backward compatibility.

Your requests are probably better placed here

https://code.videolan.org/videolan/vlc/-/issues/25640
https://code.videolan.org/videolan/vlc/-/issues/24246

Or if you really wanted to, you should be able to write a quick batch file to modify the manifest using ResHacker.