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
Sketchup.file_open always add the model to the history of opened models in the UI (menu File).
It would be useful to have an option where the API method does not log the file to the history menu. For instance, FredoBatch processes files and may open many models in a row. In many cases, this can be temporary files which are then deleted.
With this option, plugins like FredoBatch would not mess up the history list.
The text was updated successfully, but these errors were encountered:
Fredosixx
changed the title
[Request] Sketchup.open_file and model history
[Request] Sketchup.open_file and model history list menu
Dec 6, 2024
Semi-related, at the last Basecamp, Chaos Group presented their Ruby wrapper over the SketchUp C API:
Interesting. This must be a huge work, and anyway very useful for many purposes, beyond batch processing, like setting attributes to objects without opening the model. Although the C Api can do that, it is much more comfortable to do it in Ruby. Indeed, it would be a plus if Trimble would provide it as part of the official API suite
FredoBatch itself does not care how the process is implemented, provided the top method is in Ruby. And it does not operate specifically on Sketchup files.
However, since there is an interactive mode where the user is prompted (to select cameras, objects, etc...), there are cases where FredoBatch needs to open the Sketchup file in the UI session.
Sketchup.file_open always add the model to the history of opened models in the UI (menu File).
It would be useful to have an option where the API method does not log the file to the history menu. For instance, FredoBatch processes files and may open many models in a row. In many cases, this can be temporary files which are then deleted.
With this option, plugins like FredoBatch would not mess up the history list.
The text was updated successfully, but these errors were encountered: