Well. The parcel would have been left behind when importing styles and settings from 2012. Neither QSelect nor List will pick up any blocks that are defined in the drawing if they're not inserted into that drawing. So you can have hundreds of blocks defined in a drawing and not be able to list any. Same goes for C3D styles. Thy don't show up unless you have something drawn or labeled with the style.
For a list of blocks defined in a drawing use -Insert > ?. It looks like you have 77 blocks defined in your template.
No. Those weren't in your template. Those were ones I'd created to show you could have associative and nonassociative hatches. But I should have been doing Annotative. You can have annotative and nonanotative hatches also. But that doesn't show up in a list. You have to look at them in the properties Dialog to tell.
I'm not sure but I'd thing that any hatch created automatically by a Civil 3D routine would have to be associative. I don't think they would HAVE to be Annotative but that may be the way they are set to be created.
Ok. I thought you were saying I had that situation. safe to say if I don't list any hatches that I don't have any annotative hatches, correct?
No. What I was trying to say is that if there is an Annotative hatch associated with a block that is intrinsic to one of your styles. Then that block containing the Annotative hatch may trigger the Undo problem. I haven't had time to test that yet.
It has to be connected with one of your styles in some way. If I start from one of the OOTB templates or my template I don't get the problem. If you wanted to take the time. You could start a new blank drawing with no template and drag each style in one at a time and test for the problem after each one is brought in.
TIP: To reset the Undo list. Set Undo Control to None and then back to All. You'll lose the ability to undo past that point. But the Undo list will be clean.
Confirmed Known Issuse I'll share with you all.
Thank you for choosing Autodesk Support. Our development team has identified an issue with pan/zoom where the setting to group these into one undo does not always work. I have also located several reports linked to the issue. The ticket number is 1468729 and is linked to this case.
There are several reports of various workarounds allowing the issue to go away. Please see if they help you too.
I found other suggestions that your customers could try:
Since this is a known issue I will link it with the case from the development team. This does not mean that the issue is solved or complete, it signifies that Support has now transitioned responsibility of defect to development directly.
Some of that sounds familiar. I think if I would be using the Zoom command. I'd probably use other functions than the scroll wheel. Another tip. While it is no longer recognized, Zoom (V)max still works. This will zoom out the the maximum screen size possible without regenerating.