[Feature Request] Windows Explorer Enhancement

[Benjamin Hannon]

Would be very useful to see locked files in Windows Explorer Detail mode (column listing).
This could be something simple just signifying the file is locked in the SVN

Repository or more advanced by showing the user that has the file locked.

This could also be limited to files the current logged in user has locked.

[Daniel Sahlberg]

Getting information about a lock require connecting to the server which is a relatively slow operation. I think something similar has been discussed before and it was decided not to implement since the slowdown would be unacceptable. 

To see this information, please use the Check for modifications and the button Check repository (see https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-wcstatus.html#tsvn-dug-wcstatus-2).

Kind regards 

Daniel Sahlberg

 

[Benjamin Hannon]

Even if the polling rate could be client configurable and/or maybe in its own thread?   Default the polling to something higher to maybe 10 minutes to 1 hour default polling and have the setting configurable so each client may set their own if desired.

[Stefan]

https://tortoisesvn.net/faq.html#ovlremote

[Daniel Sahlberg]

måndag 7 augusti 2023 kl. 18:25:09 UTC+2 skrev brhw...@gmail.com:

Even if the polling rate could be client configurable and/or maybe in its own thread?   Default the polling to something higher to maybe 10 minutes to 1 hour default polling and have the setting configurable so each client may set their own if desired.

I checked the status cache and it could possibly be done in a separate thread there, with the limitation that what you see in Explorer would be "old news". There is an issue of knowing which repositories to poll - on my computer I have probably 100 different WCs (different repositories or branches). It would be completely waste of resources to constantly poll all of them so some kind of queue has to be created based on which WCs you work on. On the other hand when you open a WC you have not visited for a long time, the cache would be cold and the status would not be correct until next polling intervall (making the status rather useless).

To summarise, I think it will not be very useful and I think other issues have higher priority. However feel free to take a look at the code and come up with a solution.

Kind regards,

Daniel Sahlberg