You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently gFTP allows disconnecting from the the Local filesystem and connect to remote hosts with other protocols.
The Local filesystem protocol does not support remote connections or Hosts, so people get confused when they try to use it, the Hosts combobox must not contain an IP or hostname but a directory.
So it's possible to have 2 Local connections (Local & Remote) making gftp a traditional file manager without the powa of a traditional file manager
The Local menu should not have Open Location and Disconnect... disconnecting from the Local filesystem (in the Local "window") triggers a WTH reaction. To reconnect to the local filesystem you must provide a directory in the URL field.. using the Local->Open Location menu, there's no other way.
If you do it any other way, unexpected behavior may happen.. voodoo. It really takes a long time to understand how gFTP works.
When you select gFTP->Window 1, it means you can use the Local window as a remote connection, that's why Window 2 is selected by default (Remote window for remote connections), when you're switching between the 2 "windows", you can see some sort of voodoo happening in the Hosts combo.
I could go on and on explaining my findings, but let's limit the power of gFTP and implement to approach I'm proposing, that means goodbye to the FTP FXP stuff. This also limits the amount of voodoo that can happen.
That way it's easier to simplify the GTK transfer stuff a bit so that the GTK3 port can finally compile (GtkCTree -> GtkTreeView with GtkListStore).
The text was updated successfully, but these errors were encountered:
Currently gFTP allows disconnecting from the the Local filesystem and connect to remote hosts with other protocols.
The Local filesystem protocol does not support remote connections or Hosts, so people get confused when they try to use it, the Hosts combobox must not contain an IP or hostname but a directory.
So it's possible to have 2 Local connections (Local & Remote) making gftp a traditional file manager without the powa of a traditional file manager
The
Local
menu should not haveOpen Location
andDisconnect
... disconnecting from the Local filesystem (in the Local "window") triggers a WTH reaction. To reconnect to the local filesystem you must provide a directory in the URL field.. using theLocal->Open Location
menu, there's no other way.If you do it any other way, unexpected behavior may happen.. voodoo. It really takes a long time to understand how gFTP works.
When you select
gFTP->Window 1
, it means you can use the Local window as a remote connection, that's whyWindow 2
is selected by default (Remote window for remote connections), when you're switching between the 2 "windows", you can see some sort of voodoo happening in the Hosts combo.I could go on and on explaining my findings, but let's limit the power of gFTP and implement to approach I'm proposing, that means goodbye to the FTP FXP stuff. This also limits the amount of voodoo that can happen.
That way it's easier to simplify the GTK transfer stuff a bit so that the GTK3 port can finally compile (GtkCTree -> GtkTreeView with GtkListStore).
The text was updated successfully, but these errors were encountered: