I have noticed these commands on the right click menu - they look useful but also a little scary to manage on larger projects.
Could people tell me how they use and manage these function and what the consensus is on them - a good thing or a bad thing?
We have concluded that for making quick and dirty save as sketch option studies there is no obvious drawback, but when you you start to look at using it on final drawings of larger buildings that might have things hidden and then re-hidden it starts to become difficult to manage consistantly.
In our office we have debated the question and comeback with wide ranging opinions from not using it at all to thoughts about careful use of it. The nub of the debate has ranged around the nature of the model and whether it is ever truly a finished entity, and as such whether downstream drawings can be truly finished.
Unknown said:I have, of course, forgotten where that edit was done, and I have no idea of how later changes to the 3d will come through under/over the CVE "hide"
Unknown said: a fourth alternative in the CVE drop-down: EXPORT TO SIMPLE LINES IN NEW MODEL WITH TIME STAMPED NAME)
http://communities.bentley.com/products/microstation/microstation_v8i/f/19565/t/83333.aspx
- Bentley have created Managers to keep track of all sorts of things - why not this?
I can see myself superimposing 'overhead object' chain-dotted lines over just a few edges of solids (which are then all cache/hidden) in Back view; similarly 'existing removed' dashed lines in Cut and Forward view. Or is there a better way to do that (ordinary MS solids, not BA solids)
If there are specific workflow enhancement that you think may be beneficial, it would be best to log a Change Request with support so we can get them logged.
I am sure I will, once I have learned enough to be specific, meanwhile someone else might, on this issue ...?
I'll give you an answer to that Steve.
The transition from dynamic to cached is not linear as such during the design and construction phases have changes that mean using this very handy function has to be repeated far to often on the same element even for a minor change.
The management interface I would like to see would log the elements that had been hidden. This would allow them to be revealed and in the event of a refresh from the dynamic model would allow them to be re-hidden after a dynamic update.
This would represent a significant workflow benefit because it would remove the need to manually knock out the same groups of items each time
I'm think that at the point of a refresh the user is challenged with a dialog that highlights that there were hidden elements in the last cached view and offer the option to hide them again, ideally showing the elements that wil be hidden before the user says yes or no.
Also at present there is no way to reveal element that have been hidden, or to un-hide elements other than a complete refresh - a log would allow an element by element unhide which would also facilitate minor changes.
The effect would be much more consistant hiding of elements.
Haven't got onto this bit yet - but would History be relevant?