Wish: 'Clipping' parameter should be remembered per Detail

[Eugen]

Hello!
Here’s a wish for a better/more granular workflow when setting up Details nicely for print.
Could the ‘Clipping’ parameter of an object be per-Detail? Now, it’s globally (for all Details).

Why? In some Details, I might want an object to be clipped, but the same object should remain unclipped in another Detail.
Similar to the behavior of levels and sections, actually, which are also remembered per-Detail.

Thanks!

[alfmelbev (Alfonso Melero Beviá)]

Hi @Eugen,

We already have this request in our list. I’ll keep you posted.

[Eugen]

Thanks!
In VA3 maybe?

[alfmelbev (Alfonso Melero Beviá)]

I don’t think we will have this for VisualARQ 3… We are focusing on other improvements for it, so I think this is something for future versions

[Eugen]

Thanks!

And it looks like toggling the ‘Clipping’ parameter is not undoable…

[Eugen]

Hello! Found another bug regarding Section Attributes:
When copying a layer containing objects with section attributes (Layer panel > Duplicate Layer and Objects), the copies loose their attributes.

[alfmelbev (Alfonso Melero Beviá)]

Hi @Eugen,

I could reproduce it with Rhino geometry but not with VisualARQ objects, is it the same in your case?

[Eugen]

Yes, tested with normal geometry.
Thanks!

[Eugen]

Hi! And another wish regarding this:

• Editing a Rhino object = closed polysrf (Split, Trim, …), Section Attributes are lost, too.
  I assume this is because a new object with a new GUID is created, and there’s no mechanism yet to copy the attributes over.
  Thanks!

Ah yes: if possible, please include Section Attributes in MatchProperties (I think you have that on your list).

As you mentioned: best to unify the new Rhino and the VA section attributes, of course.

[alfmelbev (Alfonso Melero Beviá)]

Hi @Eugen,

@Eugen

Editing a Rhino object = closed polysrf (Split, Trim, …), Section Attributes are lost, too

If you use a curve to spit or trim a closed polysurface, what you get is an open polysurface and this kind of object cannot have section attributes applied…

@Eugen

Ah yes: if possible, please include Section Attributes in MatchProperties (I think you have that on your list).

We will do it. In the meantime, you have got a command doing this in the VisualARQ labs: https://www.visualarq.com/labs/.

[Eugen]

@alfmelbev

If you use a curve to spit or trim a closed polysurface, what you get is an open polysurface and this kind of object cannot have section attributes applied…

True, sectioning an open polysrf will not yield clipping hatches, but what I mean is: even when I edit the object, the clipping attributes should stick. At one point I might be finished with editing, and make the polysrf closed again. For that case I’d expect not having to re-create the attributes.
Hope that makes sense!
Thanks!

[Eugen]

Hello!
Francesc mentioned this in another thread:

@fsalla

We are aware that now there will be duplicated features with the Rhino 8 section styles, and this can bring some confusion for new and existing users. We are still discussing how to deal with that. We will probably synchronize VA section attributes with Rhino section styles, or use the Rhino section styles directly. In any case, we will still keep the VisualARQ section attributes for Rhino 7 users, since VisualARQ 3 will still work in Rhino 7.

Have you made up your mind how you are going to implement this?

If you compare your section attributes and the R8 section styles, it’s pretty good match (should be of course):

If you care to comment on this:

• Do you see this ‘unification’ as an issue, or as something pretty straigthforward?

• Will it be in the WIP already?

• Do you think you can find a solution for the initial wish:
  Wish: 'Clipping' parameter should be remembered per Detail
  Because R8 section styles are not remembered per-Detail, are they.

Thanks!

[alfmelbev (Alfonso Melero Beviá)]

Hi @Eugen,

Yes, we have been discussing about how to unify this and, if it is possible, it will be in the WIP. In my opinion it is great to have it implemented in Rhino!

@Eugen

Do you think you can find a solution for the initial wish:
Wish: ‘Clipping’ parameter should be remembered per Detail
Because R8 section styles are not remembered per-Detail, are they.

Yes, it looks like R8 Section Styles are not remembered per-Detail, so probably this is something to request to McNeel now… We still have it in our wishlist for now…

[Eugen]

@alfmelbev

probably this is something to request to McNeel now…

Well, how could I do this otherwise than posting here… Assuming McNeel reads posts in this subforum as well.
Do they?
Thanks, Alfonso!

[wim (Wim Dekeyser)]

Hi Eugen -

@Eugen

Well, how could I do this otherwise than posting here…

Please post such in the “Rhino” category where it belongs. Things will just get lost in long threads in plug-in categories.
-wim

[Eugen]

Re-posted here.

[fsalla (Francesc Salla)]

@Eugen

And it looks like toggling the ‘Clipping’ parameter is not undoable…

Hi @Eugen we have fixed this in VisualARQ 3.

[Eugen]

Thanks, but the ‘Clippable’ parameter is still not undo-able.
VA 3.0.13.19113

[fsalla (Francesc Salla)]

Hi @Eugen it should be!

(It also works with Ctrl+Z)
Are you doing it differently?

[Eugen]

I see the problem: it does work by menu Edit > Undo, but not when invoked by keyshort, which in my case is CTRL-Y (I have a german keyboard, but put undo onto CTRL-Y, because it’s the better location, like on an english keyboard).
However, CTRL-Z doesn’t work, either.

Undoing, say, a move command works here with CTRL-Y, but not ‘clippable’.