- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Don't worry much about getting back to anyone in a timely manner. Most of us are likely busy at work while on these forums, which is a dynamic scenario. Multi-tasking is pretty much a must these days. Got 2-3 longer term projects going on, and multiple shorter term projects going on, then have forum open on separate screen while all that is going on. Seems like getting busier with time, instead of more free time, so slowing down on forums to keep up with increasing work load & increasing responsibilities.
The only thing the main assembly document knows about any other documents is that they are being referenced, and after checking, if they are 'dirty', and/or need to be updated. Main assembly does not know about details within referenced documents. I am not sure how their (Autodesk) system works for checking if updates to referenced documents is needed or not. Document.Dirty status is understandable, but not sure about knowing when updates to referenced documents may be required. There is a Document.RequiresUpdate property, but I am not 100% sure how/when its value gets changed, since it is ReadOnly. I do know that if all you did was view related stuff, that does not dirty the document, and does not change the RequiresUpdate status, unless those changes were the type that gets recorded by DVR's (DesignViewRepresentation), like visibility / appearance changes.
When using Update, similar to using regular Save, it might not actually do anything, if it does not believe that it is necessary. It seems like Rebuild though, is supposed to 'do' something, even if it things that it may not be necessary. But even then, I would imagine many of the same things get checked. For example, I would assume that if a document is not Dirty, it will not go any deeper into it, but if Dirty is true, then check RequiresUpdate, then only if True, go further and update. I can not possibly know why some things in someone else's large assembly are getting updated and some are not, but it sounds like the software is not picking up a change somewhere, so it is not getting reported in a way that would change one of those flags. May need to ask Autodesk tech support about it, not sure. Hopefully others have encountered the same thing and have a readily available explanation and solution. I know I have encountered similar situations before, but do not recall doing anything super special by code to fix it. My next step would be recursive iteration with Rebuild, but that can cause extremely long processing time in large assemblies.
Wesley Crihfield
(Not an Autodesk Employee)