Opened 11 years ago
Last modified 10 years ago
#9546 new Feature request
least-recently-used entry (instead of oldest entry) should be removed from quickconnect recent servers list when entry limit is reached
| Reported by: | JessicaJLawrence | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | Cc: | ||
| Component version: | Operating system type: | ||
| Operating system version: |
Description
it would be helpful if, upon selecting from the quickconnect dropdown list of recent servers, the selected server were moved back to the top of the list. this would ensure that a server which the user is still actively using remains on the list, and only the server which has not been used the longest gets removed when a new server is added.
Change History (1)
comment:1 by , 10 years ago
| Summary: | most recent server should be moved to top of quickconnect recent servers list → least-recently-used entry (instead of oldest entry) should be removed from quickconnect recent servers list when entry limit is reached |
|---|
Note:
See TracTickets
for help on using tickets.
Alternatively, you could add a timestamp to recentservers.xml entries, update it each time an entry's server is connected to, and remove the least-recently-used entry when the limit of 10 entries is passed. This is an option if you don't like the idea of changing the order of the entries.