Standardized Product Content Locations
We have standardized where product content, stuff like collections of
components, materials and styles are stored on the file system.
On Windows, we moved the default content that comes with SketchUp
(Components, Materials and Styles) out of the Program Files directory
and placed them in the ProgramData directory. And on both Windows and
Mac, we created Components, Materials, Styles and Templates folders for
your user related content. By default, these folders are in the
following locations:
Note that if you store your content in these folders, it will show up in the
Components, Materials and Styles browsers without you having to do
anything and your templates will show up on the Templates pane as well.
Storing content in the %APPDATA% path mentioned above doesn’t trigger anything in the content tabs of SU. Storing to the %PROGRAMDATA% path still works.
This seems to be either a bug or a wrong documentation of the path (2 slashes wrong anyhow).
ressources of course in the according content subfolders of “…\SketchUp..” but this doesn’t help with the problem described above, i.e. SU doesn’t parse automatically what’s located in these subfolders.
the used <code> tag should normally avoid this… as here too.
“<” and “>” probably won’t change this.
interestingly in the HTML code there is an additional </username> at the end of the path:
with the documentation issue resolved the main problem still persists.
Copying content to the claimed path doesn’t work, i.e. is not parsed automatically in the components or materials bowser etc.:
Note that if you store your content in these folders, it will show up in the Components, Materials and Styles browsers without you having to do anything…
That was going to be my next question (because we have been told that changing the location for Materials require a restart of SketchUp, for the old enumerations to be cleared and new locations to be enumerated.)
The locations help does not mention that a restart is needed:
I also do not see anything new about the new locations as it affects the component browser behavior here: