Permanent Window Cut Plugin?
-
Jim
Thanks a bunch.
A real bread and butter app and now works as advertised.Good of you to intercede.
dtr
-
Jim: 2 questions
Will this be listed in the Extensions Index?
Should this thread be retitled?And thank you for the revision.
-
It's nice to rediscover these obscure and rare plugins and find them so useful. This one in particular as it was buried in a thread and never even got it's own post. If it were still in development, I would ask that a one step undo be added.
-
Crazzy plug
Just a note if you copy move the component after one use of Component Punch
this one don't work again with this component moved!
Seems component "Glue" state is losted
-
Pilou,
Seems you have to reglue the window (ThomThom's Superglue plugin) and then choose "make unique" and the window will punch properly after that. Although it does still lose it's orientation to glue to other horizontal planes.
-
Thx I will see that
-
That's works
-
You can modify the code so that if does retain the hole punching property of the component - but the punched hole doesn't move with it...
Line #186... add a # so it reads
#comp.glued_to = nil- from now on after a restart of SUp any newly punched-component will continue to make a hole in the same face as before.This very tool actually forms the basis of a hole-puncher I have had on a back-burner for many months...
Imaging a variant of this tool with a few tweaks, such as -Operated from the right-click context-menu if the selection contains suitable components that punch a hole in a 2D face...
Retaining the component's hole-punching properties in the original face.
Ability to limit the punched hole's "depth" [say 500mm/20" - adjustable perhaps by right-click dialog], so that if it's a component placed on a single skin wall face then there isn't a hole punched right across the room!
A way of linking the faces of the punched hole's "reveals" to the punching-component - using id attributes based on a time+rand id-stamp, and suitable observers attached to the component/reveal's-geometry - both at startup of tagged items if preexisting and as they are punched/made - so that then if you Move/Scale/Rotate a punching-component its associated reveal's-geometry transformation is adjusted to suit [that is, the 3D hole moves with the punching-component]; and also if you erase the punching-component the reveal's-geometry goes too [perhaps with a dialog asking if you want to keep the punched hole(?)]; and if you erase any part of the reveal's-geometry all of the reveal's-geometry erases - but perhaps with a dialog asking if you really want to do that, OR to recreate the punching-component's hole [therefore keeping the attribute linking]; if you Move the face containing the inner reveals hole then the reveals will stretch to suit automatically; if you distort [e.g. Scale] the edges forming the inner-hole of the reveal then this does not affect the rest, but if you Scale/Move the edges forming the outer-hole of the reveal [i.e. in line with the punching-component] then it does the same to the punching-component - e.g. moving it or scaling it to suit the changes - perhaps with a dialog asking if you want to do that...
The reveal's material etc should match those of the inner face so that the outer wall face material is not used incorrectly;...
Comments on this welcome... It's just I never finished tidying up my code for publication...
-
Thanks TIG the code tweak fixed the issue with the windows retaining their cutting and gluing attributes. The plugin you are working on sounds like a winner. I like the idea of defining punching depth. This would allow punching through single surface walls without coming out the other side. I also love the idea of being able to make changes to the components and having it reflected in the hole. Another option, if doable, would be the ability to "heal" the punch and delete the component leaving no trace of a hole. Sounds similar to the double cut plugin ThomThom was working on.
-
DoubleCut
walks off to a corner, huddles up rocking
-
I know that tt and I are working in parallel - and parallel lines never meet!
Several others - including Didier have also had ago and given up...
-
This has been a feature request for future SU releases I don't know why it hasn't been taken seriously by Google. During 3D Basecamp a few weeks ago I discussed just this with a few Googlers and pointed out that with the inclusion of solid tools in V8 it makes sense that this should be the next step.
I am aware we are talking about two different things in solids and components but there are similar outcomes.
Assume 100mm walls are modeled and grouped. chose component [door/window, DC even...] and select insertion point. Ideally the component will be created to suit 100 thick walls so when inserted both wall planes are cut at the reveals.
Move the window and the reveal moves with it. Edit the DC attributes to change height of the door and the reveal changes with it. Remove the door and the wall planes clean up....
If this could be done, it would take SketchUp into a new dimension IMO.
-
I have decided to work on it 'now' [rather than later]... already it's better than the 'base-tool' - e.g. the reveal faces now match the inner face's properties...
Watch this space - or its sibling thread............ -
That's great news, a much needed tool
-
Ay yes the famous line 186 makes the trick
-
Edit
Yes you can copy it on the same face, but not on another perpendicular face!
Glue is losted again 
-
Quick vid using component punch and 1001bits to make windows with mini blinds. http://www.screencast.com/t/MTU5NDAw
-
Edit
Curious this morning all woks fine with the line 186 -
My new 'Hole Punch Tool' v1.0 is now available here http://forums.sketchucation.com/viewtopic.php?p=271170#p271170
-
@earthmover said:
Quick vid using component punch and 1001bits to make windows with mini blinds. http://www.screencast.com/t/MTU5NDAw
Interesting, Earthmover. what did you do at the 51st second mark of the video? seems you selected a tool to remove the back face where the window punches through the wall....??
TIG - loading your ruby now. This is really going in the right direction!!!
I can't recall such an important step with SU.....
Advertisement