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.

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.

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

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.

@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.

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.

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.

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..

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

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

@unknownuser said:

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..

Ohh I see. SPLAT in ver 7.

This can take a while. So If you have version 7. DONT use it yet.

Im using the go speed thing in commit operation=true. Did use a recursive addition. will see..

be more specific? There is a problem already?

Greetings.

This is a spinoff from Hatchfaces, as can be seen here:

http://forums.sketchucation.com/viewtopic.php?f=323%26amp;t=38637

Will work with groups and components. Nested Groups and Components are not supported yet.
Can be a bit unpredictable with tiny geometry.

Big thank you to TIG, you can read in the link how he helped me with Hatchfaces and
this plugin.

Note: Running this tool having Driving dimension installed may crash su7(not tested on su8).
(not tested in ver 1.3.1 )

Ver 1.3.1..... 20 dec 2013

Jol_2dBoolean.ver1.3.1.rbz

NEW: TRIM. Remove geometry on face. ( Inverse standard mode )

NEW: EXTRUDE. Pushpull or Translate faces based on materials, through Dialog.

NEW: MANUAL. Introduction manual to get you started. Located below.

Faster algoritms for removing intersected geometry and holes, etc..

Plugin is now located in the Plugins-menu.

@unknownuser said:

I guess there is no need to over-complicate the code at this stage for adding new layers on the fly.

I don't swear by it, but it should be relatively straightforward to get a list of layers pop up in the inputbox.
I think it is a good idea you have, otherwise ALL hatches will end up into 1 layer unless moved manualy.
Putting "hatchlayer" as default in inputbox means one won't have to select layers if happy with that layer.

I put this on the todo list

Hi Kaas!

Finaly someone answered

@unknownuser said:

Maybe you could add a target layer-option for the hatches?

That should be possible. You do mean put the hatch in a layer already existing in the model?
Anyway I think layers are pretty flexible to work with.

@unknownuser said:

You could always print out the patterns + names on a sheet of paper instead.

That is a good solution, if going for inputboxes. I guess file browser is also possible, like TIG's 2d tools hatches.

Thank you for the inputs, and please don't hesitate to add more requests.

Ok..................

Aha. That sounds pretty obvious when you say it.

See if I got it right...

Let say the vector originaly has a length of 10. Then for each copy the vector.length increases with +10?
Ok. then I will have to reset the vector to 10 before doing the second group, unless using a vector.clone.

Thanks TIG.

Hi!

I have had this subject mentioned before and some similar topic have recently been brought up.
http://forums.sketchucation.com/viewtopic.php?f=180&t=38413&p=339504&hilit=copy+groups#p339504

However having some problems with above method and erasing groups, after they have served their purpose.

Using this code seams safer, but translation is off. It translates the whole new group 1ve. Instead it should translate each subgroup 1ve What am I doing wrong?

My guess is that the instance is "inserted" each time at gp1tran and moved with ve from there each time, but how do I transfer the insertion to the next spot each insertion?

This resulting group of groups(gp2) should be copied and translated again, and I get splats erasing gp2 afterwards using standard group.copy methods..

 #gp1=group1     gp2=group2  cop_times=number of copies  rents =group2.entities

	   
	   gp1ents=gp1.parent.entities; gp1defn=gp1.entities.parent; gp1tran=gp1.transformation
        #  
	    cop_times.to_i.times{|i|                 
           tgp=rents.add_instance(gp1defn, gp1tran) #using ve for transformation=no good

           tgp.transform!(Geom;;Transformation.translation(ve))
			   
			} 
			

Heh good question, havent tried. Maybe you will have to group the edge temporarely?