cm_OpenNetwork: executable file without start path (except for '\') + %S/%R = File not found!

[Fla$her]

1. cm_OpenNetwork in the active panel.
2. A file or folder is selected in the target panel.
3. 1. 

      Code: Select all

      TOTALCMD#BAR#DATA
      cd
      %T%R1
      wciconex.dll,119

      Code: Select all

      TOTALCMD#BAR#DATA
      %COMMANDER_PATH%\Scripts\Test.js
      %S1:~,0
      wcmicon2.dll,44
      
      <blabla>

      Code: Select all

      TOTALCMD#BAR#DATA
      %COMMANDER_EXE% /O /S
      %T%R1
      wciconex.dll,119
      
      :

      Code: Select all

      TOTALCMD#BAR#DATA
      %COMMANDER_EXE% /O /S
      %T%R1
      wciconex.dll,119
      
      .

      Code: Select all

      TOTALCMD#BAR#DATA
      %COMMANDER_EXE% /O /S
      %T%R1
      wciconex.dll,119
      
      <>

      Code: Select all

      TOTALCMD#BAR#DATA
      %COMMANDER_EXE% /O /S
      %T%R1
      wciconex.dll,119
      
      /

   2. 

      Code: Select all

      TOTALCMD#BAR#DATA
      %COMMANDER_EXE% /O /S
      %T%R1
      wciconex.dll,119
      
      \

      Code: Select all

      TOTALCMD#BAR#DATA
      %COMMANDER_EXE% /O /S
      %T%R1
      wciconex.dll,119

      Code: Select all

      TOTALCMD#BAR#DATA
      %COMMANDER_PATH%\Scripts\Test.js
      %S1:~,0
      wcmicon2.dll,44

      =

      Code: Select all

      ---------------------------
      Total Commander
      ---------------------------
      File not found!
      ...

[ghisler(Author)]

Sorry, can you explain what you are trying to achieve?

[Fla$her]

Obviously, I want it to work the same way in case of pressing buttons 3.b. as it does in case of buttons 3.a., i.e. without errors and warnings.

[ghisler(Author)]

The problem is that the function to launch programs (ShellExecuteEx) does not seem to like the start paths you provide. I don't think that there is anything I can do about that because it's a Windows function.

[Fla$her]

I don't see a relation with the function for %S and %R only. Why is there no such problem with the rest of the parameters?

1. Why is there no problems with the same path with %T%M or %C2, but there is with %T%R1?
2. Why is there no problem with an empty parameters field, but there is with %S1:~,0, which returns an empty string?
3. If the cursor is set to %COMMANDER_EXE% in target panel, then why is there a problem when pressing such a button

   Code: Select all

   TOTALCMD#BAR#DATA
   %COMMANDER_EXE% /O /S
   %T%R1
   wciconex.dll,119
   
   \

   , but not when pressing such a button? >

   Code: Select all

   TOTALCMD#BAR#DATA
   %COMMANDER_EXE% /O /S "%COMMANDER_EXE%"
   
   wciconex.dll,119
   
   \

4. Why is there a problem with an empty start path in cm_OpenNetwork, but not after opening any wfx plugin, e.g. \\\Registry\?
5. Why is there no error when setting \\ in the "Start path:" field, but when setting \, \\\, \\\\ etc. is there?

[ghisler(Author)]

Why does it matter? The path parameter is invalid.

[Fla$her]

Could you first answer my questions point by point? This is important to me, otherwise our conversation doesn't look productive. Thanks.

This is important primarily because some of my buttons and user commands with an empty "Start path:" field don't work properly from cm_OpenNetwork, which I open quite often.

[ghisler(Author)]

Sorry, i do not have the source code of Microsoft's ShellExecuteEx function, so I cannot say why it fails with some start paths but not with others.

[Fla$her]

That's how you can answer only points 4 and 5, but not 1, 2, 3, where the problem is clearly related to the implementation of TC parameters.
That's why I asked you to answer point by point, because your answers don't explain the logic of behavior when the factors coincide.

[ghisler(Author)]

Sorry, this cannot be resolved because it occurs outside of my code in ShellExecuteEx.

Moderator message

Moved to will not be changed

[Fla$her]

2ghisler(Author)
Explain why you haven't answered my 1,2,3 questions? How can the work of ShellExecuteEx be related to the parameters that affect your code? Are the %S and %R parameters your code or ShellExecuteEx?

There is an assumption that these parameters, unlike the others, change the typing in such conditions, so ShellExecuteEx does not perceive them.

[Fla$her]

2ghisler(Author)
I would like to get a quality response to the previous post.

[ghisler(Author)]

I have checked this now in the debugger: TC passes the directory of the active panel to the launch function. When using any of the list parameters, TC uses CreateProcess to launch because it supports much longer command lines. When using %N or %M, it uses ShellExecuteEx. The latter seems to ignore invlid start paths like \\Network, the former doesn't. I will pass the system drive as start path instead of \\Network to fix this.

[Fla$her]

I will pass the system drive as start path instead of \\Network to fix this.

OK. Wonderful! Then it's worth moving the topic back.

[white]

Moderator message from: white » 2024-10-10, 11:02 UTC

Moved topic
» from TC Behaviour which will not be changed to TC11.x bug reports (English)