You can't access physical file system from script commands (except <tgmove command). So adding Exec.exe to VP is an easy way to run any physical files w/o adding them to VP.
MVV wrote:You can't access physical file system from script commands (except <tgmove command). So adding Exec.exe to VP is an easy way to run any physical files w/o adding them to VP.
I see, but the problem is that if I add Exec.exe to VP then location to the physical file is stored without %COMMANDER_PATH% variable for instance. And I am using portable Total commander, so I have to add Exec.exe every time when I open Total commander from different location.
MVV wrote:Well, it is a weighty argument.
Perhaps I could add some flag for <exec comand for starting physical programs...
I would be very happy if you do so. But anyway thank you for nice plugin, and sorry for spamming you all.
Also with scripts, you can build one that create/rebuild the tools folder taking into account COMMANDER_PATH. You put something like following script inside \Tools virtual folder :
Horst.Epp wrote:I'm using Virtual Explorer with the adapted bar file for it functions
and only "cd \\\VirtualPanel" to show and use the contents.
I never used the the entry "Virtual Explorer" which is
VPBatch.exe with parameter ^explore .
This works but its menu doesn't contain icons for most of its buttons.
Only a few are displayed as Icons but all buttons are working.
Same problem here. I am not using Virtual Explorer very often, but noticed today that most of icons are missing in the toolbar, but buttons are working. The icons are only visibles in Virtual Explorer TC32 but not in TC64.
It works fine for me with TC 9.0a 64 bit and VP 2.0.7.1370 on my working TC installation and with clean installation.
Which version do you use? Can you reproduce it with build 1370? Please prepare a tiny portable TC installation (archive) with VP installed where the problem may be reproduced... I think it may be caused by some configuration options or different icon libraries.
Hi I have a node with space in the name. >Export Test
I want to export this entry only so i use the following command: <export /f "C:\temp\export.vps" ">Export Test"
i get 0 exported entries
If i do the same with no space in the name this works correctly !
I just renamed my script as : >Export_Test <export /f "C:\temp\export.vps" ">Export_Test"
If I have both >Export and Test nodes, both are exported instead of the one i want !
It seems that space is interpreted as separator for multiple mask even if no curly braces enclose it.