You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PLEASE get the libraries out of Program Files. Windows 10 does not take it well when changes
are made to Program Files. I am able to put files in and not be able to see them with Files
Explorer but can see them with a text editor. Even after a reboot, I can edit the files but
not see them in Explorer and the IDE cannot find them. This is a Windows design feature
but you are exacerbating it by using Program Files for data storage. Library code is data. It can change. When debugging a library, it can change frequently. Windows does not handle this well.
This action is against the philosophy of Windows re the Program Files folders. They are for code, not data.
The text was updated successfully, but these errors were encountered:
If you need to add libraries, you should add them to your sketchbook, in the libraries subdirectory (not sure where that is stored by default on Windows, but it is shown in the preferences). If you need to modify a built-in library, copy it into your sketchbook and modify it there, the copy in your sketchbook takes precedence.
I don't think that supplying builtin libraries and other code in program files is a bad idea, those files are not meant to be changed. If you insist that they are moved out, where do you suggest they should be stored? And how would you suggest that upgrades are handled if you modified a library?
PLEASE get the libraries out of Program Files. Windows 10 does not take it well when changes
are made to Program Files. I am able to put files in and not be able to see them with Files
Explorer but can see them with a text editor. Even after a reboot, I can edit the files but
not see them in Explorer and the IDE cannot find them. This is a Windows design feature
but you are exacerbating it by using Program Files for data storage. Library code is data. It can change. When debugging a library, it can change frequently. Windows does not handle this well.
This action is against the philosophy of Windows re the Program Files folders. They are for code, not data.
The text was updated successfully, but these errors were encountered: