Pasting file path -> error

I'm an Altap Salamander user and used to paste file paths to quickly change directories and select the file indicated by the name. Unfortunately, WinSCP does not support it as smart as Altap Salamander does: WinSCP shows an error when trying to paste a file path - "Directory '<pasted-file-path>' doesn't exist.".

Could you please extend WinSCP that way that at least it will select the directory of the pasted file path (and as a bonus select the file)? Thanks in advance.

Dear sir,

I got a error for compile winscp 5.11.2 version, i mention that error in below pls give me a solution for compile that source code.


[DCC Error] PasTools.pas(387): E2361 Cannot access private symbol TCustomForm.FTextHeight
[DCC Error] PasTools.pas(392): E2361 Cannot access private symbol TCustomForm.GetTextHeight
[DCC Error] PasTools.pas(547): E2361 Cannot access private symbol TCustomListView.FMemStream
[DCC Error] PasTools.pas(547): E2008 Incompatible types
[DCC Error] PasTools.pas(558): E2361 Cannot access private symbol TCustomTreeView.FMemStream
[DCC Error] PasTools.pas(558): E2008 Incompatible types
[DCC Error] PasTools.pas(569): E2361 Cannot access private symbol TCustomRichEdit.FMemStream
[DCC Error] PasTools.pas(569): E2008 Incompatible types
[DCC Error] PasTools.pas(592): E2361 Cannot access private symbol TApplication.FAppIconic
[DCC Error] PasTools.pas(597): E2361 Cannot access private symbol TApplication.FAppIconic
[DCC Error] PasTools.pas(602): E2361 Cannot access private symbol TApplication.FMainForm
Failed
Elapsed time: 00:00:03.3

Thanks for your report.
I will take a look at this issue.

srinivasan wrote:

I got a error for compile winscp 5.11.2 version, i mention that error in below pls give me a solution for compile that source code.

Can you start your own thread for your problem?
This has nothing to do with the topic of this thread.

martin wrote:

Thanks for your report.
I will take a look at this issue.

Unfortunately, this bug still is reproducible in 5.11.3. Is there a corresponding issue in the tracker?

camper wrote:

Unfortunately, this bug still is reproducible in 5.11.3. Is there a corresponding issue in the tracker?

This request (it's not a bug) has been added to the tracker:
https://winscp.net/tracker/1593