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
TrguiNG has some great advantages over other RPC clients, particularly speed and the ability to handle adding several .torrent files at once. Kudos!
One area of usability that is a pain point on macOS is that the autocorrect is very aggressive. The search bar will constantly try to change partial word matches to the closest dictionary word. For example, entering a valid substring like ethio
in search, it is replaced by Ethic
which won't match the desired the file.
Pressing [F6] (Move Download) and typing a pathname like
/downloads/joe
will immediately be replaced by /downloads/Joe
which is a problem. I'm guessing there is a way to specify to the underlying APIs that text fields should be handled as literals and not subjected to the system-wide autocorrect. Please consider this!
The text was updated successfully, but these errors were encountered:
TrguiNG has some great advantages over other RPC clients, particularly speed and the ability to handle adding several .torrent files at once. Kudos!
One area of usability that is a pain point on macOS is that the autocorrect is very aggressive. The search bar will constantly try to change partial word matches to the closest dictionary word. For example, entering a valid substring like
ethio
in search, it is replaced by
Ethic
which won't match the desired the file.
Pressing [F6] (Move Download) and typing a pathname like
/downloads/joe
will immediately be replaced by
/downloads/Joe
which is a problem. I'm guessing there is a way to specify to the underlying APIs that text fields should be handled as literals and not subjected to the system-wide autocorrect. Please consider this!
The text was updated successfully, but these errors were encountered: