why dose this happen? bug in 2016?
actually, I think its always done this.
FIX!!! FIX!!! FIX!!!
Why would the change not be reflected in the drawing?
If you create the dimension even though it points to the wrong location, the dimension will change with the part. Then create a note and pick the dimension while the note is active. This will place the dimension in the note. Now you can hide the the original dimension. The hidden dimension will update with the changes to the part which will in turn update the dimension in the note. At least it has for me.
I too am annoyed with this always happening. One work around I use is to just dimension the radius and then I add a note with a leader, click on the dimension to add it to the note then add another branch to that. After that hide the original dimension and you are all set.
we also use annotation note method, always ends up biting us in the ass when model is changed and not reflected to the drawing.
WOW! your pretty tricky Jim
Sorry I wasn't clear enough but that is what I was trying to say when I said "click on the dimension to add it to the note" above
This won't address this particular issue, but it's a good idea to turn this setting on anyway for more predictable behavior:
That said, adding jogs to leaders sometimes has a different set of behaviors. I'm seeing what you are seeing when I tried this out. The arrow is pointing to the circle, but it is pointing to the invisible portion as if the circle was extended all the way around. Please contact your VAR to have them evaluate this behavior and possibly file a bug report for you.
Yep, that's pretty annoying! If anyone gets an SPR for this, please post it here. I'll "vote" for it.
The workaround in the technical comments does solve this problem, but it sucks that we have to do it in the first place. On the other hand, it's better than adding a note and linking it's text to the radius dimension that gets hidden.
SolidWorks Corp investigated Greg's particular issue and identified it as SPR 488068 specifically. Just FYI.
SW's behavior when it comes to this and multi-jog leaders has always been wonky and it drives me nuts. I really wish they would fix this! This SPR has my vote.
Additionally, back when we had 2015 I used to be able to get this to work without any crazy work-arounds. The option highlighted below sounds like maybe it's meant to control this, but for me at least, turning this off or on doesn't seem to have any effect:
Retrieving data ...