Hi there !
First of all thanks for making plugins.
Which version of SU is needed to run the plugin ?
Doesn't seem to work on SU Make 2015.

Cheers

probably same reason as this...

Link Preview Image More mac 'Color' panel woes

there are many ways to end up with <auto> colors in SU… I wrote an extension that hopes to aleviate the fustration caused… it assigns new names using a javascript color names library… but, on my mac, although the colo…

favicon

SketchUp Community (forums.sketchup.com)

john

Of course !! Thanks Tig

What is your problem - can you provide a sketchup model.

Thanks guys - this gives me some good direction. I like Sam's strategy where he makes use of the raytest.

@fredo6 said:

> tr_axe_inv = Geom;;Transformation.axes(face.vertices[0].position, *(face.normal.axes)).inverse >

Neat! Just saved fifteen lines of code in a script...

Sorry,

Start and commit are not nested. A few lines of debug code proves that.
Still at a loss.

Contact me directly through CabMaker32 website

Link Preview Image Contact | CabMaker32Contact – CabMaker32

favicon

(cabmaker32.com)

My client wants to be able to stop the process. I've got him copying a file named stop.txt into a folder. I check it every loop. Works great.

I have now coded the dynamic attributes into my plugin for bifold doors.
There was a gotcha that I wasn't expecting. It took me a lot longer to understand what was going on.

I started out just calling the script over and over to create up to 4 doors which handles a double bifold. Three problems, code was starting to get messy, execution was starting to take more time and memory and storage was increasing too much.

So I now create 1 door create a second instance then flip it. Then take the bifold (2 doors) and instance it and flip them. This caused havoc. As soon as I tried (in code) to change the axes of the second door the door no longer behaved as expected. Turns out that Rotz on the flipped door changed from 0 to -180 and all I did was flip the door.

Of course if you flip the door in the editor the rotz stays at 0.

flip the sibling

tr = Geom::Transformation.scaling(sibling.bounds.center, -1, 1, 1)
sibling.transform!(tr)

If I change axes after flipping door then the door moved to an unexpected place. If I change the axes before flipping the door the axes gets flipped as well causing the door to move over.

The solution I came up with was to create a parent container to hold the door. Flip the door. Since the parent's rotz stays at 0 I could reference the grand parents angle.

Creating another level of nested containers effectively insulates the animate coding from the effects of flipping the door.

From a time complexity perspective I think the problem is inherently O(n^2) (which means that your code can't be any simpler), also, if the curves have few segments and you already know enough to throw away half of them, then I would say your code is probably close to optimal. In general, the simplest way to gain speed is to use bounding boxes in various ways like reducing the input to segments in the bounding box intersection between the curves and so on, however, there are constant costs associated with this so it may not be a gain on small inputs.

@garry k said:

JQL
Flip along axis is great however, if the component has an interaction like rotate to simulate a door opening then you will find that the component reverts back to it's original state (you loose the flip).

What I need to do is change axes.

Funny doesn't happen to me. But I don't question your need to change axis.

Error 101 means the internet connection time out on your computer. Stairmaker needs to connect to my web service once every week.

I was hoping to do a POST because I will be updating a database with my real JSONP call.

Unfortunately when I do a check on the php side I see that the call is turned into a GET.
I agree that a timeout and an on error function is a good idea.

My main question is will this work with OSX Lion. I was hoping that someone could try it out and tell me.

When it comes to push pull I understand that it does depend upon the winding (clockwise or counter clockwise) of the polygon. This is consistent and repeatable.

However, with an extrusion that has a closed polyline as a path it is not repeatable. I can guarantee that the points for the face are always created exactly the same way - since they come out of a txt file. I store x and y points at 1/10000 decimal inches. The z values are set as 1/2 of the height of the door panel.

I also calculate the path as x and y points which is a closed polyline. The Y values are 0.

face = group.entities().add_face(face_pts)
path = group.entities().add_curve(path_pts)
face.followme(path)

If I build the door at [0,0,0] look at it and then do a ctrl_z and repeat this process, I get a results where the the extrusion is sometimes reversed and sometimes not.

It appears random - although the polyline and face are always created exactly the same way.

When I create my curved stair stringers using fill_from_mesh I store each polygon's points with a clockwise winding. So far this has proved 100% predictable and repeatable.

In the early days I used to do a lot of work with GIS and Windows GDI and create polypolygon this way. If you wanted to create a continent with a large lake that has an island that has a body of water you would have a series of 4 diminishing polygons each completely residing within each other. The outer most polygon would be clockwise (the continent) the large lake would be counter clockwise, the island would be clockwise and the body of water in the island would be counter clockwise.

I found that the sketchup works essentially the same way with meshes.

@dave r said:

Garry, that looks good.

@krisidious said:

I hate construction points... Mainly because it's such a pain to get to them and delete them.

Really? Edit>Delete Guides is too difficult? How about doing what I did and make a keyboard shortcut.

I thought that only deleted guides... I didn't know construction points were "guides", thought that was for construction guide lines only. Nice to know. 👍

Thankyou - this will be a good read!

I currently test on SU 7, SU 8, SU 2013 and SU 2014. The work around is easy enough.

By default a texture's 'grain' always follows that axis, so your make-the-parts-rotated_and_then-rotate-them-into-place method is a winner. 😄
I think in your case it's the best approach...

However, FYI you could also change the orientation of a texture for certain faces 'in code' - just like you might when using the manual 'Texture' tool - from the context-menu when a textured face is selected.
I [and others] have written several UV / Texture tools - which move, scale and rotate textures - look at their code for ways to transform some UVs and then apply them to a face.material.texture...
http://sketchucation.com/pluginstore?pln=TextureRandomizer
http://sketchucation.com/pluginstore?pln=TIG-TextureTools

TIG,

I didn't need the parallel code. I wanted to return the original pts and the flattened one

pt1 = @ip1.position pt2 = @ip2.position p1 = Geom;;Point3d.new(pt1.x, pt1.y, [pt1.z, pt2.z].min) p2 = Geom;;Point3d.new(pt2.x, pt2.y, [pt1.z, pt2.z].min) eye = Sketchup.active_model.active_view.camera.eye ve1 = eye.vector_to(p1) ve2 = eye.vector_to(p2) return [pt2,pt1,p2] if( ve1.cross(ve2).z > 0 ) [pt1,pt2,p1]

My test

New version 1.0.49 now available for download

Version number now shows up on title bar of web dialog Now uses same License strategy as cabmaker Check license now first deletes old license and then updates license Has preferred setting for users who have license issues