I just checked on an older PPC mac. So to sum up this thread: ` # Sketchup Ruby OSX 10.4 PPC * RUBY_PLATFORM: fat-darwin8.8.0 * RUBY_VERSION: 1.8.5 Sketchup Ruby OSX 10.5 Intel * RUBY_PLATFORM: i686-darwin8.10.1 * RUBY_VERSION: 1.8.5`

I think it is a typo, as it is the ALT key on Mac. tested with a simple tool.

Hopefully, this file will work. It uses the system call ShGetFolderPath or ShGetSpecialFolerPath to retrieve the folder, so maybe the paths will be localized. @thomthom said: But on XP the folder names for sure is localised. I can try later today on my old laptop with Norwegian XP. I'd be interested to see if it works.

There is no scripting API for layout, no.

@thomthom said: Like AJAX solutions often do? This approach is most often used for "inter-frame" communication. If there are 2 frames in a page that are hosted on different domains, the JS in one is not allowed to access the other, but many browsers allow you to change the fragment identifier regardless of security, so it might work in this case. (There are a handful of other mechanisms people have used to get around frame-2-frame security, and any of them might work. Searching on the topic might give us a clever workaround.) Ajax apps will often modify the fragment to maintain state in the URL, so you can still email URLs around and have your friends land on the same "page" inside an Ajax app.

thanks, I'll give that a try. David update: Chris, thanks! that worked perfectly.

This is somewhat troublesome. One would then have to be very careful when creating observer instances. Ideally only create one instance - ever, if possible. And also clean up any references the observer has to other objects when possible, as otherwise they won't be GC'd either. grumble refactoring time.

ooops!

Me stupid

@dan rathbun said: @thomthom said: @dan rathbun said: (1) Jim did not subclass from Sketchup::ShadowInfoObserver No need. Su doesn't care. Just implement the methods required. I knew that Sketchup does't (currently,) check the observer's superclass. But isn't it a matter of good Ruby programming practice? And, what if (in the future,) Google implements some built-in methods, constants, etc. in the superclass that will need to be inherited by your custom observer's subclass(es)? You'd have to go and edit and re-release all your plugins that use observer's. Kind of seem to be by design: http://forums.sketchucation.com/viewtopic.php?f=180&t=17047&start=150#p171636

@gavvy said: em~~ Gaieus Maybe you don't know the pass of them. I love Sketchup Very Much,and they claim they are "China Sketchup Official website".why? And much other things of them OK, that explains much! Sorry for my ranting!

And again. This time bar should have been @foo.bar.

@thomthom said: And it really is counter-intuitive the way Ruby 1.8 works. Agree! .. but at least they revising Ruby to correct things the way they should be.

@davidboulder said: This isn't data that will just pop up while something is running. It would be on the screen while the user is working on the model. This rules out view.draw_text as this can be done only inside a custom Tool, and the user would be using other tools (standard and custom.) @davidboulder said: ... but I thought a screen overlay head's up display for some data would be slick. Might be... but some users find overlays annoying, and would want a way to turn them off. @davidboulder said: I guess my third option is just to keep the data as part of a dialog box; Best idea is a Webdialog. The user could have it floating anywhere, resize it to their liking, and close it when they wish. FUTURE: Perhaps someday the API might include a dockable DataBar class (similar to the StatusBar.)

As if documenting the entire API wasn't crazy enough, here's crazy idea #2 - create a mock-up Ruby library of the entire SketchUp API (called Mock-Up, naturally.) Document the source code classes, methods, constants, etc as if it were actual code (because it is.) Generate docs from source code. With the potential added benefit of being able to test SketchUp plug-ins outside of Sketchup.

Unfortunately the built-in 'delete guides' menu item removes all guides [lines and points] in the model - including any in groups or component-instances [including locked ones] and even guides stored in 'off' layers - however, guides within a component definition that has no instances in the model are safe... Two years ago I wrote a set of context-menu tools to deleted guide-lines / -points 'selectively' - here's an update ConsDeleteContext.rb I would also be possible to write a new tool to 'preserve selected guides' - it would duplicate them in a new definition that had no instances [with a bit of vertical 'edge' ([0,0,0],[0,0,1]) at the origin***], later you could choose to 'restored preserved guides' and it would place an instance of that component [at the origin, erasing the temporary 'edge' there ? *** I haven't quite worked through how the guide-component 'insertion' point is kept for later reinsertion - but it will be possible], then explode the instance and then delete that component-definition's entities, thereby purging it from the component-browser's list. Of course purging the model's unused components in between times would delete the preserved-guide component and the saved guides would be lost - just like copying something new to the clipboard loses the current data. The 'preserve selected guides' would be like using the clipboard and it'd overwrite any already preserved, but it could be set to warn if there is an existing preserved set [i.e not yet restored] that'd be lost in the process, and it'd ask you either to overwrite the set or to add these new guides to the existing set ? Unfortunately I'm stowed under will other things, and I'm unlikely to be able to look at this before sometime in June! - but if anyone wants to take up the ideas feel free...

hmm... interesting... have you tested any of the unusual candidates?

I prefer unompressed output as the codec when compiling to a movie file will compress it. If you JPEG compress the stills you'll end up double up with compression artefacts.

@thomthom said: It would help if you posted the syntax error you get. It includes indication to where in the script you have errors. And when you post code snippets, please wrap it [code] tags in order to preserve formatting and ease of reading. Hey sorry i edited my post before i saw yours because i found a snippet that i didnt include and i thought it best just to ask someone who knows what theyre doing

TM's? Sometimes its painful to help when I have to ask more questions about your jargon than about your sript issues