Jeff D The more I think about it, the more I see that "refresh per Selection Set" is The way. Very logical. The work flow you describe is just one use case. Persisting changes to the 'custodial work' or tons of 'embellishment' that is required to make what DV/BV outputs usable has been dicussed many times in the past. The other way you could do things is to 'smart copy' the Drawing model contents that is generated by BV / Drawing Rules. If the Drawing Model is Ref'f as a CVE, you have the option to Copy/Hide elements. Why not use the copy process to convert the annotation elements into slightly smarter annotation elements. The smarter annotation element would allow the user to 'lock' whatever he wanted. Maybe, the annotation text would be automatically converted to Fields that point at the original BV/DR produced text. You could even use Mstn's Named Group logic to make each bit of information either active (any changes mad to the info automatically propagates to the other members of the group) or passive (any changes from other members of the group will update the local info, but any local changes will not propage to the rest of the group). Converting the 'graphic-centric' Text into 'data-centric' Fields allows the user to rearrange the way the information is presented while retaining the vital links and dependencies that are needed to synchronise the information. The way Mstn's DV's and by extension BV's already work a bit like this by generating 'proxy graphics'/Element Handlers that provide diffrent representations or resymbolisation of the same element. A beam is represented one way in 3d, another when its cut, another way when its resymbolised as single lines in a structural layout etc etc. What you are experiencing and want to do is not new. I think you will find that it is the tip of the iceberg in a BIM environment, where you will need to synch with others across disciplines / silos.
↧