Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Renaming files: windows re-selects entire filename when other files resync
Found a reproducible annoyance in Windows 10 with Dropbox. I often cycle through a lot of folders using the tab key to rename them one at a time, and this produces an issue where, as soon as the Dropbox app has synced the previous file, Windows highlights all text in the currently-being-edited filename, even if I am tapping through it.
To reproduce:
- Open a folder containing many files that is currently synced in Dropbox
- Click on a file name twice (not doubleclick) to begin renaming it. Rename it however.
- Press the Tab key to flick down to the next file in the folder. If the previous filename was still in the 'editing' mode then you will automatically be editing the next filename.
- Quickly start using the arrow keys or Home/End to move around in the filename but do not start typing
- After a second or two, when the Dropbox App has re-synced the file you previously renamed, Windows will highlight the entire filename that you are currently arrowing-around in - maybe just as you were about to start typing.
I suspect this has something to do with updating the little blue and green file icon overlays.
If you were just about to start inserting some text somewhere in a filename, but hadn't started typing yet, then the fact that the filename has just re-highlighted itself might cause you to overwrite the entire filename instead of inserting the part you were planning.
When doing this with many files this can be a real annoyance. Is a fix possible?
- Hey AntennaMan!
Thanks for following up with us!
It looks like this is not a Dropbox specific issue, and it's appearing with other cloud programs as well.
Now, it'd be wise to note, that since this isn't an issue caused by Dropbox or pertaining just to us, we're not able to provide a precise solution.
I'd definitely suggest checking in with Microsoft about this, as well just to make sure you've exhausted all options and to also let them know about this.
Give me a nudge if you have any other questions!
94 Replies
Replies have been turned off for this discussion
An update - This still a problem ... again.
This issue seemed to go away for me for a while and I posted in this thread that it fixed for me.
But soon after (a week or two), the issue was happening again. I just didn't get around to re-posting.
So yeah, this is still very annoying. And I agree with Fr0stbyte5 that solutions for this should be possible, like a user changing the frequency of the updating.
i.e. A user can find a threshold where conflicts would be very unlikely (Dropbox would even be able to recommend a time, calculated by folder shares + frequency of updates per user, etc), but where the refresh issue is non-existent.If I can make a recommendation to the Dropbox team, this is one of those issues that *SEEMS* small and likely very insignificant vs adding new features that could attract new users and revenue streams, but this is actually quite a big annoyance, and the ONLY annoyance that I have when using Dropbox, so if this problem was to be elevated in priority and addressed, then I'd not be surprised if you find retention increasing and churn decreasing.
Do some 'quality of life' updates to keep your existing customer base happy, and in turn create ambassadors out of them. Because right now, if someone asked me for a recommendation, my response would be "Yeah, it's good, but ..."
Get rid of that 'But', and good things could just happen.
"A bird in the hand is worth two in the bush"Classic Business ethics to defer the problem to another software company. Fair enough when it is in fact not the fault of Dropbox. It's annoying when they might know the solution, but can't answer because of liability reasons.
Fortunately I found a solution on a microsoft thread. Apparently it's caused by the Microsoft Search service, and all you need to do is simply disable it.
Here's the original thread where I found the solution.
thank you very much
Disabling Windows Search makes no difference for me - bug still present.
