Ability to delete and replace a Plugin object style within the resource manager without converting an existing parametric object to 'Unstyled'

[Pvz11]

Hello, 

 

Is VW looking into the limitations for 'Styled' objects and are they looking to improve them? If so we want to note what we believe there is a fundamental issue with replacing styled objects within the resource manager. We have a feeling others have noted this is the past but we wanted to push this forward again.

 

We've noticed this for a few VW iterations that when you delete a 'Plugin object style' within the resource manager IE Door style/ window style etc etc... If the style is assigned to an object within the active VW document it will then set that parametric object to 'Unstyled'. 

 

We work on 'High rise commercial residential buildings' which are normally 5 - 8 floors at a minumum however we currently have some projects which are 14-32 stories high.

 

The issue we have is that we have projects where the styled plugin object is deleted within the resource manager and then without the user noticing or they just simply forget, a large segment of doors (& other parametric objects that have a style assigned) etc is then converted to 'Unstyled' within the active VW document. 

 

To clarify we tend to use 'design layer viewports' for layers where the entire floor is truly identical & repeated on design layers for each floor, I am more so referring to where the plans and layouts are different for each floor however the assets we use are exactly the same specification which is where we use our styled plugin types.

 

To stop this from happening we were hoping for the ability to have 'styled' parametric objects to be able to be replaced properly from the resource manager much like traditional black symbols. In this case for the new 'Style' within the resource to replace the previous style for every parametric object within the active VW document that the previous style was assigned to.

 

We understand that there are methods to reduce this from happening such as doing a 'custom modification command' or using the 'select similar tool' however the point of the style object is having the ability to control hundreds if not thousands (on some projects we've had) of styled doors etc which can be controlled without issue. Adding a workflow to additionally search for assets introduces 'human error' within our checking procedure for our models which can be significantly reduced by having the same logic as 'replacing symbols'.

 

Thank you you very much for your time, apologies for the lengthly post this for us is and has been a consistent issue.