Selection bug or not?

[Anonymous]

Does anyone know if this is a bug or is there a system variable that can change this , open the attached drawing at the zoom level it opens at window select the red circle. While the grips are active (blue) zoom out. note the dimensions that are now also select? Repeat starting at different zoom magnifications and note only dimensions that are completely out of the display are selected, if any portion of the extension  line is visible that dimension will not be include in the selection set.

[john.vellek]

Hi @Anonymous,

I copied and pasted everything into a new drawing and I cant get the same behavior so I think it is likely something with your drawing.

What do you think? Give it a try and see if this works for you too.

Please hit the Accept as Solution button if my post fully solves your issue or answers your question.

[elshawadfy]

Hi @Anonymous,

It's because of the way "DIMORD" works.. it places a point in the origin from from where the coordinates are measured (the origin of the current ucs when you created the dimension), which happens in your case to be the center of the circle..

Try the following:

1- move any of these dimensions by the move command (not grip editing), and select it to see the grips, you'll notice 2 things:

   - The readings don't change when using move (because the origin moved with the dim)..

   - there is a second grip where the center of the red circle used to be..

   - If you grip edit any orf the two points, the readings change.. (because you either moved the origin, or moved the measured point separately this time)

2- Try the command UCS, pick a point for the new ucs, and hhit enter twice to accept the rotation an it is, then try "DIMORD", you'll notice: .

   - a new grip where your UCS are..,

   - The measurements are taken from that reference point not from the "GWS" or the original UCS..

3- Hit "zoom" extents" and see how the drawing looks.. Now Try UCS, then W to return the ucs to it's original state, and try "DIMORD".. Now try Zoom Extents again, you'll see the drawing became too small and you can see the origin within, thats because "DimOrd has placed a grip..

Notes:

-- That point put in the current UCS disappears after exploding the dim..

-- Beware to not move or modify the dims by accident by selecting their origin (As you were about to do) - it's better to lock their layer for safety if you're finished with them..

-- Beware of the current ucs when placing "DimOrds to net have faulty readings..

-- Beware of copying or moving "DimOrdinates", their value will remain the same as the original because the origin moved with the Dim..

Regards 🙂

[imadHabash]

Hi,

Try this:

- Let your UCS at World 

   Command: UCS
Current ucs name: *NO NAME*
Specify origin of UCS or [Face/NAmed/OBject/Previous/View/World/X/Y/Z/ZAxis] <World>: w

- Then type Plan then enter.

I think it will be OK.

I hope so...Good Luck

[Anonymous]

Okay let me explain my problem, I get drawings from many companies and I program a laser. I try to reuse as much geometry and as many dimensions as possible. Since many drawings I get were created in 3d programs like Inventor and solid works there is always line segments i need to delete when I put the views together to create my flat pattern. When I go to  delete these line segments I zoom in real close and window the area that may contain the items I need to delete. If I do not have the dimensions on an isolated locked layer, and zoom into a point that the extension line from the dimension is no longer visible and window any  dimension node the dimension is deleted along with what i was trying to select. Try this if you would, draw a rectangle say one by one, dimlinear pick one horizontal and a vertical line and place dimensions, now zoom into the the point where the extension line in no longer in the display window, invoke the erase command window select the corner of the rectangle that as a dimension node in it. If you find that a dimension  was not select I would really love to know why!  In the sample drawing I have attached try this select erase command and in the left view port window select the A and B to be deleted. 

Thanks

Joe

[elshawadfy]

Hi @Anonymous, 

I didn't quite get what you wanted at the end of your previous topic, selecting the corner results in selecting the dimensions because of the nodes that are there - and that's normal..

But in general: In every drawing,

1- Create a layer for dimensions..

2- Use the filter command (fi), select "dimensions" and "add" then "apply"

3- In the properties palette of the dimensions: change the layer to that you created for dimensions..

4- Lock the layer when you're not working with dimensions..

That would be the best practice in my opinion..

Regards..

[Anonymous]

That what I thought, a bug. See my idea of normal is window selection means the entire object is in the window, and normal crossing means any object that is partially or completely in the window is select. The idea that windowing around a node is the same as the entire dimension is not normal that what I call a bug! And locking the layer has been my only work around. I tried  changing the offset from origin but that doesn't work with ordinate dimensions   Thank you for your response!

[elshawadfy]

Hi @Anonymous,

Ahh!! now I get what you mean.. I didn't catch that you were talking about "window" selection as opposit to crossing..

And yes you're right, I think you should report it..

You can also add a wish in AUGI to change that behavior

Regards 🙂

[Anonymous]

Zoom in on the red circle and try again in the drawing you pasted it into, all dimensions that have there extension lines out of the display window will be selected. At zoom extents nothing will be selected zoom 5x (pan to circle is in center all x axis dimensions except 0 will be select. At different zoom levels and different placement of the red circle will result in different selection sets. But with window selection only the red circle should be selected no dimensions, crossing selection will be different but my problem is with window selection.

[john.vellek]

Hi @Anonymous,

Did you try copy and paste into a new drawing? I couldn't duplicate the problem when I did it. I think it is just the one drawing that has a problem.

[Anonymous]

Hi John,
Thanks for getting back yes I did try copy and paste. But I must just be doing a poor job of explaining myself or hopefuly there is a fix for this. Did you see the other example I sent (selection problem 2.dwg). I keep trying to make this simple but it's not working, try this new drawing any templet! Dimlinear pick any two points on the screen, zoom in on the node at pick point one or two to the point where you can not see any part of the dimension except the node, no part of the extention line is in the display. Now invoke the erase command now window select only the node not crossing hit enter. Do you still have that dimension? I tried this with several .dwt's went to a friends shop and down loaded the 30 day trial of 2017 on my home computer, everyone gave me the same result. Window around the node should not select the dimension! If as any part of the extention line is in the active display it will not select!

[Anonymous]

Hi John,Thanks for getting back yes I did try copy and paste. But I must just be doing a poor job of explaining myself or hopefuly there is a fix for this. Did you see the other example I sent (selection problem 2.dwg). I keep trying to make this simple but it's not working, try this new drawing any templet! Dimlinear pick any two points on the screen, zoom in on the node at pick point one or two to the point where you can not see any part of the dimension except the node, no part of the extention line is in the display. Now invoke the erase command now window select only the node not crossing hit enter. Do you still have that dimension? I tried this with several .dwt's went to a friends shop and down loaded the 30 day trial of 2017 on my home computer, everyone gave me the same result. Window around the node should not select the dimension! If as any part of the extention line is in the active display it will not select!

[Anonymous]

Hi John,

If still in not sure what I am talking about I tried to improve my sample drawing, here is the new version!

[john.vellek · Accepted solution]

Hi @Anonymous,

I see what you are describing. I believe that if you select the  point that establishes the dimension measuring point, it is going to behave as you see happening in your drawings.

The simple thing is to lock the dimension layer so you can't inadvertently select the node.

I have not noticed this before but this behavior goes back to 2013 if not older products. (That is the oldest version I have installed)

Please hit the Accept as Solution button if my post fully solves your issue or answers your question.

[john.vellek]

Hi @Anonymous,

I am checking back to see if my post helped you with your problem. Please add a post with your results so other Forum users can benefit.

Please hit the Accept as Solution button if my post fully solves your issue or answers your question.

[Anonymous]

Thank you, yes it was good to finally have the problem confirmed, I thought it was just on my end but as you can see zoom in close enough and the window command behaves like a crossing command on dimension nodes. I wonder if this started when they changed the way dimensions exploded, back I am not sure how long ago when you exploded a dimension it left the nodes behind then they changed it so when you exploded a dimension the nodes were deleted. The oldest version I can confirm this happening on is 2008, but I have been using AutoCAD since R9.

[john.vellek]

Hi @Anonymous,

I can't confirm when or whether this behavior first appeared. I go all the way back to version 1 but my brain doesn't always remember such little things. 🙂

At any rate, I tested back to 2013 which is the oldest software I have installed. This tells me that it is current and "as-designed" behavior that is likely to remain in current product.

Please select the Accept as Solution button if my post fully solves your issue or answers your question.

[Anonymous]

So glad to see this got fixed in 2018! I would like to think I had something to do with this getting fixed I have versions back to 2008 that has this problem now wit 2018 I can not reproduce the problem! 🙂