logo
NOTICE:  This is the new PunchCAD forum. You should have received an email with your new password around August 27, 2014. If you did not, or would like it reset, simply use the Lost Password feature, and enter Answer as the security answer.
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
ZeroLengthCurve  
#1 Posted : Thursday, December 13, 2012 12:40:31 AM(UTC)
ZeroLengthCurve

Rank: Senior Member

Joined: 5/15/2008(UTC)
Posts: 989

Thanks: 19 times
Was thanked: 37 time(s) in 25 post(s)
My drawings have innumerable and undwiedly layers and branches. I find myself often creating new geometry or construction aids on layers I wish I had not. A simple way to help users avoid this might be a right-click option as well as in-screeation tream "Set Default Layer to object selected or nearest the start/end point of new geometry"

So, if new lines or other geometry are within some user-defined radius of an object, the user could be prompted. But, since Tim won't know everything a user might want, there could be an ascent list something like:

-- nearest geometry having no apparent intersection
-- nearest geometry having no overlapping objects
-- nearest solid (or other geometry, from a drop-down list of valid, VCP-managed objects)
-- nearest center of gravity of any type of object
-- nearest color, etc

Edit: So, suppose I have the Inspector open. I select some geometry by filtered color, or by direct selection. The Inspector could temporarily un-collapse and present the "Layer" area of the palette, and, along side the Layer field, a newly-minted checkbox could appear: "Set as new default layer or by-color task session?"

Edit 2: Or, instead of explicitly changing the default layer, user the in-stream idea to make new geometry to onto the layer of the touched, temporary-parent geometry, but then "flag up" the new geometry onto a running summary palette table that shows the previous 5-10 created items individually or by structural association. This way, it would be easy to "knock out geometry on some distracting mesh", since a lot of my tasks involve removing meshes and replacing them with new surfaces based on polylines or on splines, assigning the same color and them to the same layer. Work flow could be sped up.

Yes, I realize that code stabilization is very, very important. But, I think that some of these ideas should have been implemented ages ago, and during code clean-up, some of these might fit in without too much testing needed.
Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.