DimAngle snapping problem - SOLVED

Hi!
Here’s an annoying little problem with DimAlign:
It prompts you to click the first, then the second line, that’s the way it works. If you then click between the lines, the angle dimension will be the short angle (say 30°), and if you click further outside, it will be the long angle (330°).

Now, if i want to use snapping to place the angle dim on the same radius as a neighboring angle dim, it is somewhat undefined or glitchy if the dim will be the short or the long angle…
I guess it’s because when the snapping point lies exactly on the line, some tiny floating point precision value will decide over which side the dimension will be placed.

How about adding a toggle to the command that forces the angular dimension to switch between inside/outside?

Thanks!
Best regards
Eugen

Seems like a reasonable thing to do. I’ll see what I can figure out about that.
I don’t like adding more controls, but maybe it’s needed.

Thanks

Thank you!!

@Eugen - I didn’t want to add another option to the command, so I made this so that when you snap to a point on one of the lines, the direction you approach from controls which arc you get.
Can you take a look when we get another build out - probably next Tuesday - and let me know if it works for you?
Thanks

Hello!
Sounds good, I will check it out, of course! Thanks for the quick fix!
Best regards
Eugen

RH-38285 is fixed in the latest WIP

Hi!
Do you mean 6.0.17066.1228? (which is the latest downloadable WIP, right?)
I just checked - still the same problem. See screenshot.
Thanks!
Best regards
Eugen

@Eugen - It is possible to get either arc predictably. It depends on where your mouse is when you approach the snap point. Here’s a video - https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/3/f/3ff0c8008d01e06971aaa8261cf9bb2bdee0508c.mp4

Hello Lowell!
Thanks for the video! I understood exactly what you mean anyway, in the first place. However, it does not work reliably (yet). I tried it out thoroughly.
I’m using 6.0.17066.12281 - does the fix come with this version?

Thanks!
Best regards
Eugen

@Eugen - I think not in that version.
It will be in the WIP from yesterday, March 14, which I think is 6.0.17073.13071

Lowell is correct. The fix is in the very newest WIP from yesterday.

Installed the latest WIP (6.0.17073.13071) and voilá! Works just fine now, thanks a lot for the fix!!
Best regards
Eugen

Glad to hear that it works for you