you need a few more def's and wrap it all up in a class.

class MyClass #replace with your preferred name

def gui()
  #...code
  log = UI;;Command.new("Load log file") { load_log_file() }
  #...code
end

def load_log_file()
  @logPath = UI.openpanel("Open Log File")
  if @logPath
    x = File.join(@logPath.split('\\'))
    readLog(File.join(@logPath.split('\\')))
  end
end

#... other defs

end #class MyClass

I think something could be possible after import...

Still only one (sorry). I'll be happy just to get this one released, and then add the functionality once I get the API for the javascript figured out. It may be another free/pro dual offering...

Actually, I hit a block at the renaming functionality. Click-drag is used to organize, and click is used to activate the scene, leaving not much else for renaming, other than adding a row of links under the scene name (or icons beside the name) for accessing the various features. The icons could be a possibility.

Thoughts?

Sorry, I'm not sure what you are trying to do.

@dialog = UI.webDialog.new
@dialog.show()
@dialog.visible? # returns true if the dialog is visible

This will tell ruby that the dialog is open, but I don't think that's what you were asking. What do you need to accomplish?

EDIT: After a few more readings, I think I may have figured it out You could use @dialog.execute_script(javascript_goes_here) that could set a js variable to say the html was opened from SketchUp.

I started one, and even thought about combining the two - may do that in the (hopefully near) future.

By way of update, all that's left is to save/retrieve settings in the model.

readLog(File.join(@logPath.split('\'))) if @logPath

would do the trick, but I suspect you have a block of things to do if @logPath is valid, hence

if @logPath
   readLog(File.join(@logPath.split('\\')))
   # other stuff here...
end

or an entity (like a face):

model = Sketchup.active_model
sel = model.selection   # have something selected
model.active_view.zoom sel.first

Sketchup will zoom to the selected object.

I've updated the GGroups docs

While it could be done, I'm having waking nightmares about models with thousands of scenes.

The real trick would be creating the algorithm that would be smart enough to filter out the 99.9% of the camera positions that wouldn't be necessary, and capture the correct .1% that would be useful. Again, not that it can't be done, but it would take some doing. One way might be to have a minimum distance between camera positions, or minimum angle divergence, or combination of things...

It's not a problem with split(), but with value assignments: somewhere in your code, there's a problem assigning a value to "@logPath. Since @logPath is 'nil', then it isn't anything that can be acted upon.

For the free version, it is coded to use anti-alising and the default compression quality setting, whatever that is.

For the Pro version, I've gotten some good testing feedback, and have added options for antialiasing, compression quality, file overwrite notification, and saving the settings into the model & retrieving saved settings. If all goes well, it will be released early next week.

SceneExporter(free) will export the scenes in your model to a jpeg image, using the drawing window resolution as the image size. Scenes not part of the slideshow will not be exported, allowing the user to control which scenes are exported to image files.

A "Pro" version is nearing completion that adds a webDialog to allow users to preselect scenes to export, along with specifying the image size and file type. Clicking on the scene name in the list will display the scene in the SketchUp drawing window so you can preview the image before (de)selecting it. There are several preset image sizes and optional aspect ratio locking for custom sizing. The dialog auto-updates as you add/remove/rename scenes, and remembers the last used settings.

I took a look in the model.options list, and nothing there looks promising (I didn't expect it to, since what you want aren't really model options. If I have a chance, I'll do some more checking tomorrow, but I don't expect positive results...

Would it be easier to have an observer that automatically adds to the opposite face as you paint a face? Naturally, it could be turned on/off.

Thanks!

Meanwhile, I am collecting the suggestions...

Basically, the paths work like this:
The camera will be set up at each vertex on the camera path. So, if you have 23 edges in the path curve, there will be 24 camera positions (one per vertex).

If the target path has the same number of vertices as the camera path, the target will be at each vertex. Otherwise, the target point will be interpolated along the path so that there are the same number of target points as camera points. For example, if the target path had only 3 edges (4 vertices), the whole path length would be divided mathematically into 23 equal segment lengths, and the target points would be set at equal distances along the 3 edges.

Hope that makes sense...

Okay, I was wrong on request "A": oddly enough, there is no way to remove scenes via ruby, so the undo scene creation option won't work. You'll have to do things manually (for now).

The "remember camera only" is still possible, just need to code it.

Unfortunately, that will have to be a v8 feature request. I can make that request (and I think it's a worthwhile one), but it won't be available for some time. For now, the best that can happen is collecting everything inside model.start_operation/commit_operation.

Sorry...

Yeah, I'm a bit slow lately. 8-month-old baby + overtime at day job = not much ruby time
It will get done eventually...

So, basically, you could be calling hundreds of changes to edges (hidden/not hidden), flooding the undo stack (limited to 100 operations) and basically eliminating the undo capability. I can see why that would be undesirable

IIUC, you want the changes to not be part of the undo stack at all, but the one option I know about is to trap all the changes in model.set_operation/commit_operation so they appear as a single undo item. The only thing relating to geometry manipulation that is "transparent" from ruby (that I know of) is the group.move! method.