Who at @TomTom thought it was a smart idea to store everything TomTom HOME related on Windows under %USERPROFILE%\Documents filling up document storage (especially hard when you have a cloud backup!) with some 100 gigabytes.
It should have been at level %LOCALAPPDATA% at best.
It should have been at level %LOCALAPPDATA% at best.
A friend asked me to help figure out why his cloud storage ran out of space.
TOMTOM used 99% of his document storage space. These are not even documents at all: just map data either downloaded or from the device.
%LOCALAPPDATA% or even better %USERPROFILE%\AppData\LocalLow
TOMTOM used 99% of his document storage space. These are not even documents at all: just map data either downloaded or from the device.
%LOCALAPPDATA% or even better %USERPROFILE%\AppData\LocalLow
You should get your Windows developers acquainted to CSIDL and KNOWNFOLDERID.
CSIDL is deprecated but usually has better descriptions of the values than KNOWNFOLDERID: docs.microsoft.com/en-gb/windows/…
Use FOLDERID_LocalAppDataLow or FOLDERID_LocalAppData, not FOLDERID_AppDataDocuments
CSIDL is deprecated but usually has better descriptions of the values than KNOWNFOLDERID: docs.microsoft.com/en-gb/windows/…
Use FOLDERID_LocalAppDataLow or FOLDERID_LocalAppData, not FOLDERID_AppDataDocuments
KNOWNFOLDERID documentation is at docs.microsoft.com/en-us/windows/… and points to the corresponding CSIDL values, if any.
In addition, newer versions of TomTom HOME should migrate old data to the correct locations.
I know that's hard, but software development is.
In addition, newer versions of TomTom HOME should migrate old data to the correct locations.
I know that's hard, but software development is.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
