A ‘dirty flag’ for the entire storage (internal or external) might be possible.And in a lot of cases it could help.
But it might not - depending on how you access your Fuze, you might find the filemanager you use to look at the content drops invisible little desktop.ini files all over the place to tell it how to display the folder next time you visit it…
Sadly, even some *nix filemanagers have started doing this nonsense BY DEFAULT! Yes KDE Dolphin, I’m looking at you, you PoC!!
I’ve only used Windows Explorer for modifying internal memory, and this occurs without actually looking at the expansion card, only the internal memory.
Also, if I DO use Windows Explorer to look at the expansion card, but don’t actually modify the contents of internal memory, no database refresh is done.
This happens in both MSC and MTP modes.
By the way, the Sansa Connect handles this beautifully. When you connect it to your PC, it creates an MTP connection but leaves the Connect menu available for playing songs, etc. One of the menus shows the counts of playlists, artists, albums and songs on the player. When you copy a song to the player (either to the internal memory or the expansion card), you see the counts increase as expected … in other words, it refreshes its database WHILE you’re syncing media to it. When you detach the player, it doesn’t do a database refresh at all, regardless of whehter you updated the internal memory or the expansion card.
Unfortunately the Connect’s firmware was developed by Zing (now owned by Dell), not SanDisk, so I know they can’t lift this bit of the firmware and transfer it to the Fuze … but it does prove that it’s possible.
Message Edited by PromisedPlanet on 01-26-2010 09:04 AM