64-bit context menu

[Filehero]

Yeah - one more important step towards adressing one of those recurring "issues".

to Don and Mesh.
Btw, I for one found myself really surprised what entries are coming up in "x64" context mode.

Question: why isn't it possible to display the XY custom items in the 64-bit context menu? Basically the entries are configurations (known at render time), so they should - at least theoretically - be displayable in the x64 context as well, right? I don't want to indicate it's an easy task, I'm just trying to understand.

Anyway, smart and smooth move.


Cheers,
Filehero

[Enternal]

Amazing!! Thank you to Mesh & Don!

EDIT: Don, I'm curious but how come you're sending the file path to the ContextMenu64.exe using a temp file instead of just sending it directly to the executable? I don't know for sure or not but it might be the reason why there seems to be a slight delay to the context menu loading compared to the 32Bit context menu. Also, if there is a reason, perhaps deleting that temp file afterwards would be ideal?

[admin]

Question: why isn't it possible to display the XY custom items in the 64-bit context menu? Basically the entries are configurations (known at render time), so they should - at least theoretically - be displayable in the x64 context as well, right? I don't want to indicate it's an easy task, I'm just trying to understand.

I think it would be possible but it would require a complex two-way communication between XYplorer.exe and ContextMenu64.exe (and between me and Mesh). Additionally parts of XY would have to rewritten to allow MLS in the menu. And whenever a new custom item would be added to XY's menu, Mesh would have to add it as well and recompile ContextMenu64.exe, send it to me, we would need version control, etc. horror!!

No, let's keep this simple. There is still the chance that XY will become 64-bit anyway...

[admin]

EDIT: Don, I'm curious but how come you're sending the file path to the ContextMenu64.exe using a temp file instead of just sending it directly to the executable? I don't know for sure or not but it might be the reason why there seems to be a slight delay to the context menu loading compared to the 32Bit context menu. Also, if there is a reason, perhaps deleting that temp file afterwards would be ideal?

This is for multiple selections. You can pop a context menu for thousands of files. This cannot be done via command line directly. It's the same trick that use for the external copy handlers. The temp file is deleted when XY exits.

[eil]

congrats with this huge step i guess! now most of 64-desires should be glad.