[Plugin] 2dBoolean ver1.3.1 beta UPDATE 20 dec 2013

jolran

Pilou is a Luddite and still often uses v6 - he's asking it the tool will work with that too.

Ver 6 is a bit old..

TIG

Use this to avoid a crash
begin model.start_operation("2dboolean", true) rescue model.start_operation("2dboolean") end
Then it should work in v6/7/8...
BUT your 'version trap' should also work ???

jolran

No it crashes ver 7. I will try your trap.

jolran

Your version did not work either It not related to that problem, muted the other items so the was only one start operation, still crashes...

This can be difficult problem to spot. Typical

TIG

I have just tested it in a v7 SKP with your code intact... and it worked fine!
As it ought...
Duh!

jolran

I get big instant splats all the time?? Strange that it works for you.

Anyway, I will test it more later on ver7. Don't have ruby code editor installed there, so testing is a bit painful. Won't make much difference anyway since it splats all the time

Edited: Well done some tests now. It's very timeconsuming to start up sketchup from a crash every time..

So. It crashes on a more than 1 place. Where I erase the groups gp3, and gp. NOT the components(comps) wich was a little surprising. Also it crashes when making group to component at the end. Really? I haven't been doing this for long, so I can only feel sorry for you scripting guys when you only had to work with SU7. It feels very unstable compared to su8.
That's not an excuse for me to make it work for ver 7, though. IF it can be done..

TIG

So you have SketchyPhysics installed in v7?
If so try disabling it... and retest...

jolran

Hah! Well spotted TIG!!

It did not exactly have SketchyPhysic installed. BUT i temporarily moved all plugins in a different folder and then it worked!
So it was in the same category of problem you where thinking at.

Now, I guess I will move the plugins back one after the other to see which plugins is producing the hassle.

I think I learned my lesson here... Should have tested it in ver 7 before releasing.

TIG

Do the testing 'by halves' it's quicker as you exponentially zoom in... 'one by one' takes longer...
You must have a script loading that's messing with the group base class methods ???

EarthMover

Very nice Jolran. I'll test it out and give a report back.

Thank you!

jolran

Well. I have found the 1 plugin that cause the crashes. Unfortunately I can't remember where it belongs to.

It's scrambled so there is no additional info. Anyway ldd.rbs is the name of the file.
I'll update it in the starting info.

jolran

@unknownuser said:

You must have a script loading that's messing with the group base class methods ???

Haven't got a clue yet. I guess the only way is to test where 2dboolean will crash?
Doing it 'by halves' as you say.

@unknownuser said:

I'll test it out and give a report back.

Please do, Earthmover!

A part from this tool's bugs and issues, it would be nice to hear reported info about how big file sizes and performances are in a "real life" projects. When using edges instead of materials in Layout and so on.

TIG

The 'ldd*' greps to Ledas's 'Driving Dimensions', which probably does mess with several base classes, perhaps ill-advisedly - the earlier .rb versions I've seen certainly did! ...
As far as I can see your tool is not doing anything at all 'awkward' then I suggest that you PM the DD author about this issue...
I loaded the latest DD with the .rbs files into v7 and it breaks your tool AND my EEbyRails etc and my olde Mirror tool - which also use some group copy code too... So there could be potentially many issues uncovered here
I'll PM Dmitry Ushakov...

jolran

Well there you go. Driving Dimension it was. If I remember correctly I uninstalled DD because of some crashes, this file must have been left behind. I will update this in the starting page.

@unknownuser said:

I'll PM Dmitry Ushakov...

Yes please. That would be good. I'm sure he would want to know, since it's not breaking only the 2dboolean script.

Thank you.

jolran

BTW(If you would read this). Is it working for you, Pilou?

pilou

I obtain that with the V6, but I don't very well understood what must be inside the rectangle ?
An image, a texture, a color...? (here it's a texture)
Result is on the right

TIG

In your example the 'face' is the blank top of the box, the 'group' is the face with the grouped 'image' material.
Select both then run the tool
The result is that the grouped 'image' is trimmed to fit on the select face
If the grouped 'image' were smaller and arrayed like tiles then the whole lot would would be trimmed...like this

jolran

Ok. I should have made a better tutorial about this. Sorry .

Tig has illustrated the whole purpose of the tool.

It might not be clear WHY use this tool when you visually can get the same result from a material IN Sketchup. BUT when used with Layout to simulate vector color and edges, for printing you will get much more precision in quality.
And edges can be used with styles. So some pretty nice sketchy effects can be made.

This tool wasent originaly designed to use whole faces to texture and color things, it's an intersect tool for edgepatterns.
From that perspective, modeling all those edge-patterns each time can be very tedious, so hence this tool..

The main difference compared to Sketchups internal intersect tool is that the face materials are kept, by turning them into a cutting component.

I'm experiencing a little inconsistency in the intersections(you can call it a bug), so I will have a look at that.
Faces with holes dont get erased at times.

pilou

So I have made the exact inverse
Now all works like a charm in the V6!
Bravo!
Except you have created a group (the initial group floating in the space with texture in my case now empty but always present! )
that you must kill after the process!
You can only kill it with the Outliner!

jolran

Nice Pilou. From judging at your pictures, that is the desired behavior of the plugin.

What do you mean exactly? There is a group I have forgoten to delete? Or maybe that you cannot select the component, except then in the outliner? The second alternativ was corrected by defn.invalidate_bounds.
But maybe that method doesent work on SU6. Do you have this problem on all su versions?

If you doubleclick the component in the outliner (to enter the group) and then exit again, the boundingbox will be reset.
But that is just a workaround if this method doesent work on older su versions.

Thanks for the feedback Pilou
Please test in on holes and such.. It should work on all standard axis(Su views), but sometimes it fails on "in between" angles. I'm working on a solution to resque if the calculation fails.