Of course. In the meantime I also found the right solution. This Sketchup is very powerful when you found the correct sequence of commands script! Thanks again. I think for my project (some ambitious) I will still need your advice. I hope that you are always online these days as then. Bye

If you don't use @xxx in front of the variable name it will work - xxx. If you use @xxx the last values you entered are remembered. Don't mix @xxx and $xxx like this - I recommend you stay with @xxx. However, you must assign the @xxx values before the dialog first runs - like this [###=changes] choose=[ "Frente 1", "Frente 2" ] @choose="Frente 1" ### set initial [default] @choose enums=[choose.join("|")] ### you just could use emuns=["Frente 1|Frente 2"] prompts=["TIPO","Ancho","Alto","Espesor"] @a=600.mm if not @a ### set defaults for @a - any changes to @a will be remembered for that session of SUp... @b=709.mm if not @b ### @c=19.mm if not @c ### values=[@choose, @a, @b, @c]### results=inputbox(prompts,values,enums,"Parametros del frente") return nil if not results ### 'nil' @choose,@a,@b,@c=results ### $a >>> @a etc ########### Frente 1 pz=[] pz[0]=[0,0,0] pz[1]=[100.mm,0,0] pz[2]=[100.mm,-@c,0]### pz[3]=[0,-@c,0]### edges=entities.add_curve([0,560.mm,0],[@a,560.mm,0],[@a,560.mm,@b],[0,560.mm,@b],[0,560.mm,0])### a >>> @a etc facez=entities.add_face(pz) facez.followme(edges) ### etc etc

Sounds like a plan to me!

TIG- I am on a PC though trying to do a similar thing for the mac. I'll try some observer fun but am sure to be splatted into oblivion Thanks for your thoughts. best, Justin

Oops, came here from "new posts". Got to read those subject titles better. I took a couple of swings at ruby, then put the bat back on the rack before my hands blistered

Thanks!!! Now I can continue with my project!!

@chris fullmer said: Are you going to work on a multi-user SketchUp environment where the server database holds the actions of all users and pushes that info back out to all other users simultaneously?????? Eh, noo... not for now. Your idea is nice, anyway . What I need is to store information about materials, dimensions and other characteristics of some predefined objects that will be created. And to be able to alter that data using a webdialog interface. What is this post here? Because I find this http://www.tmtm.org/en/ruby/, but there I could find just linux packages. I don't know what I'm looking for... I just don't want to use a lot of programming languages. It's enough to me that I'm forced to use that ugly JavaScript for webdialog

Make sure you've downloaded the most recent version of the script. This thread is for 1.2, which is obsolete now. The current version is 1.3 and its here: http://www.sketchucation.com/forums/scf/viewtopic.php?f=180&t=11212&start=0&st=0&sk=t&sd=a Chris

...correction four... ...now that might come in handy.

Thank you, TIG. There was a small problematic part I could not handle, so I copied it from your cleaned-up version. And you're right... sometimes I spend too much time looking for a script to automate a task or a 3d warehouse model that suits my needs, when I could have done it manually in half the time. But I highly recommend "extend close lines". It really saved me time with this drawing. And Todd, thank you for checking out this odd case. I'll continue in the Smustard forum.

It already exists... http://www.sketchucation.com/forums/scf/viewtopic.php?p=40025#p40025 Put the fast_tw.rb file in the Plugins folder: 'fast'=it's the quickest way & 'tw' = TextureWriter To use it you just type fast_tw <enter> in the Ruby Console. Any material textures in the model (whether used or not) are then extracted into the model's folder as jpgs etc...

context sensitive

Thanks Adam - I am actually trying your program as you speak as an example of what the display could look like and it looks great but I am not looking for a lighting tool. My equivalent "lighting effect" is created by custom radiation functions that depend on the type of source, the distance from the source, and blockage and are not light sources. I am not lookig for photo realism but for a representation of intensity on surfaces. The essence of my question is: what technique could be used to color small portions of the Sketchup drawing? The resolution I am looking for is typically 30 cm square for drawings that are the size of a building. Is there some way to divide up each face of every entity and assign a color to it based on the result of my "radiation function" as the point. Perhaps this is part of the infrastructure you mention? Thanks for your help.

Organizer is just trying to load the .rb files it finds in the subfolders of your Plugins menu. The usual fix is to explicitly exclude subfolders that are created by other plugins. You can do this by adding the subfolder's name to the "SmustardOrganizerExcludeFolders.txt" file. If that doesn't fix it, contact me at Smustard and we'll troubleshoot it.

Yes, it has been that way since the first release of Ruby back in June 2004. We ask every release for that to be fixed. The good news is that with V7, we did get a larger COURIER font for the Ruby Console instead of a smaller ARIAL font or whatever it was. Perhaps I can do some more smooth talking with the Google developers and get them to fix this too. It is quite annoying, and really does slow performance on long running traces. Todd

@thomthom said: I'd be very happy if SU8 focused on stability, bugfixes, GUI and UI improvements pluss more ruby power. I totally agree with you thomthom. Fix the core problems - we can always count on this community to develop cool new features! BTW - I used one 20-inch monitor with SU for a long time and have recently gone to two 22-inch widescreen LCDs at home and must say it is wayyyy more enjoyable now since I can really spread out and put all of my palettes on one monitor and model in the other. Never going back!

In your example e = edge... there are several ways of doing everything in Ruby... edges.each{|e|e.erase! if e.valid?} # is the same as... edges.each{|edge|edge.erase! if edge.valid?} # is the same as... edges.each{|edge| if edge.valid? edge.erase! end#if } So 'each' of the 'edges' - called 'edge' (or whatever) is processed in turn inside the {}: 'edge' as a variable doesn't survive outside of the {} unless you declare it outside of them later... It's become something of a standard to use |e| as 'entity'... However, whatever text is inside the the || it is used as the variable you are interested in. It CAN be anything 'legal'... Sketchup.active_model.entities.each{|e|puts e.typename; puts "the next entity..."} here 'e' is the same as 'entity' Sketchup.active_model.entities.each{|entity|puts entity.typename; puts "the next entity..."} I comes down to choice and clarity - if you use it briefly the 'e' might be fine, if 'e' is drifting about many lines of code later, then you might have prefer it to have been called 'edge' or something clearer... mats=[];Sketchup.active_model.materials.each{|material|mats.push(material.name)} mats.each{|e|puts e} ...

Ah... ...was kind of hoping you'd say no here, and we could expect an speed update... oh well. Just had a brainwave while doing some sandboxing.

You get .php some times because the link goes to a PHP script which redirects you to the download. When that happens you have to link the link instead of Save As.

@thomthom said: @tig said: EntitiesObserver onElementAdded ? Then I'd have to monitor every group and component definition and the model object. I'm not that familiar with the overhead of Observers. But this sounds like it'd be quite a lot of observers running... Anyone knows what the performance impact of doing this would be? I think it's a worthwhile experiment to create a meta-observer (built on the existing observers) that watches a "class" of entities - such as a GroupsObserver, or something like that.