Unfortunately v2017 changes the way references can be got and reused. A few pointers... Use: entities = model.**active_**entities Also you can 'grep' to filter many kinds of 'collections' thus: puts face = entities.grep(Sketchup::Face)[0] return nil unless face The 'face' reference is lost in v2017 after the 'explode', instead consider this... group.explode puts face = group2.explode.grep(Sketchup::Face)[0] Now 'face' is a different, but valid, reference... I added the 'puts' to print the references in the Ruby Console. In < v2017 they should be the same, but in v2017 they will differ. This issue has meant that many authors have had to recode some of their plugins to accommodate the changes...

Does it happen if you have only your plugin loaded?

@alexmojaki said: Incidentally, I haven't tested any of this on Windows yet, so we'll see what happens when I try there. This might not be over yet. Aaaand...I'm back! Indeed, this solution doesn't really work on Windows, because as soon as window.blur() is called, it doesn't just remove focus from the dialog, but from the whole Sketchup application! Sketchup goes into the background, yet somehow it is the window that is open according to the taskbar, and if you click on it in the taskbar to try and reopen it it minimises it.

OK...it doesn't crash if just before showing the savepanel I put a line of code to show a simple messagebox: then the savepanel shows. Although the messagebox is nowhere to be seen. Then I tried this code: if UI.messagebox("Save results to file?", MB_YESNO) == 6 savePath = UI.savepanel("Save results file",model.path,"Sunlight analysis.csv") # If the user doesn't press cancel; if savePath outfile = File.new(savePath, "w") outfile.write(allResults) outfile.close() end end Now when the execution reaches this point SU suddenly switches program, i.e. as if someone had pressed Alt+Tab. It's still there, but I have to reopen it. And the messagebox still isn't anywhere, hence neither is the savepanel. I just seem to have gotten the UI very confused in general.

Well.. it returns white on Win7 because that IS the system dialog background color "out of the box". (One reason I hate Windows 6+ is they try to make dialogs look like webpages!) Anyway.. a user can set their own theme, or download a premade theme from the Web, in which the dialog background may not be white at all. The other day, on XP, as a test I changed my system dialog color to Purple, just to test that method, and it worked, it returned the purple color that I had set. And SketchUp also used that color for background of it's dialogs and toolbars, etc.

Sweet, thanks.

If the transactions between the two scripts are in one session without any need to remember things for the next session then why not make the two scripts within the same module and pass @arrays between them ? module Mojaki def self.script1() ... @faces<<face...etc ... end end#module AND in another file module Mojaki def self.script2() ... @faces.each{|f|...etc ... end end#module You run the scripts as Mojaki.script1() etc as needed... The @faces array is remembered/accessible between the two scripts because it's in the same Module... So as script1 makes/changes it, script2 can read it...

@alexmojaki said: Also glad to understand what soft and smooth edges are. For a detailed breakdown of what each property does (soft and smooth has very distinct functions) check out this article: http://www.thomthom.net/thoughts/2012/06/soft-vs-smooth-vs-hidden-edges/