Putty session non-modal?

Hi,

would it be possible to have the session non-modal, so that one could go back to file-handling without loosing the session's output etc...

Would be a big time-saver for me ;)

Tx

Michael

Doy ou really mean Putty session or the WinSCP console window? Because putty is is different program.

Sorry for being not clear: I was referring to the terminal-window you open with Ctrl+T

Anonymous wrote:

Sorry for being not clear: I was referring to the terminal-window you open with Ctrl+T

Hm. I can consider this. But it is not easy thing to do. Also note that the window is closely connected to panels. If you change path in the window (using cd command), the path changes in panel too. What if you were copying the files at the time?

Hmm, the way I use it most often I don't make use of that coupling-feature. So if modal or not was an option, it would be ok if "non-modal" would also mean "independent of panel"...

Anonymous wrote:

Hmm, the way I use it most often I don't make use of that coupling-feature. So if modal or not was an option, it would be ok if "non-modal" would also mean "independent of panel"...

Then you can use "Open in PuTTY".

But then I would loose the nice and convenient dropdown command-list which also remembers history across sessions :(

OK. Maybe if more people ask for it... ;-)

OK, great - now come on, all you hidden lurkers and shout "Me too" ;)

9 years later...


I would like the WinSCP Console window to be modeless, so that I can continue to manage files and sessions in the WinSCP's main window. Currently I have to open a new separate instance of WinSCP to circumvent the modal behavior of the Console window.

Ideally dialog boxes should only be modal, if they cannot be modeless. The rule of thumb is to keep them modeless unless it's mandatory for the user to complete using the dialog and close it before the user can continue using the program that created the dialog.

In this case, nothing in the Console dialog makes it mandatory to be closed first before I can use the main window. I should be able to use both windows at the same time. (Also, I don't see the said behavior of "current directory synchronization" happening. I executed "cd.." and the main window's directory didn't even change.)

ADTC wrote:

Ideally dialog boxes should only be modal, if they cannot be modeless. The rule of thumb is to keep them modeless unless it's mandatory for the user to complete using the dialog and close it before the user can continue using the program that created the dialog.

In this case, nothing in the Console dialog makes it mandatory to be closed first before I can use the main window. I should be able to use both windows at the same time. (Also, I don't see the said behavior of "current directory synchronization" happening. I executed "cd.." and the main window's directory didn't even change.)

While you are right, changing this is very difficult. As only 2% of users use this feature and most of them are probably not limited by the modal dialog, I do not think it pays off reimplementing it.

Me too!
I created a custom command to start a server. This command takes about 10 minutes to start the server. Every time I run this custom command, I need to wait for 10 minute before I can do anything in the main window of WinSCP

The latest version of WinSCP has new feature that allows running local custom commands with paths to remote files.
Using it you can off-load time consuming tasks to a separate process, like WinSCP script or PowerShell script using WinSCP .NET assembly.
See Extending WinSCP with Custom commands that run .NET assembly or WinSCP script.