MoI discussion forum
MoI discussion forum

Full Version: Angle Numerical Entries Problem

Show messages: All  1-6  7-15

From: Elang
6 Nov   [#7] In reply to [#5]
That's surely works, Michael!

Only thing is it takes 3 steps for expectedly simple creation.
Moi3D is loved for its intuitive UI, so I believe it's better to keep it that way. ;)

Sincerely.
From: Michael Gibson
6 Nov   [#8] In reply to [#6]
Hi Elang,

re:
> Also, Michael... IMHO, most of Moi users will expect that the '<' input tab should> consider the starting point of line creation rather than 0 is the +X axis (?).
> The '>' tab almost never used for rotation purpose, isn't it? Or maybe it is just me... ^^

The current behavior to use 0 being the x axis is modeled after polar coordinate entry in AutoCAD.

> I think something like r99 (turn right 99 degree) or l99 (turn right 99 degree) should
> be convenient and easy to understand.

That seems good, then it could also work to give a distance value like 5r99 = distance of 5 from the previous point and angle of 99 degrees from the previous line.

- Michael
From: Elang
6 Nov   [#9] In reply to [#8]
Hi, Michael

>then it could also work to give a distance value like 5r99 = distance of 5 from the previous point and angle of 99 degrees from the previous line.
That's even better !.. Yes, please! ^_^

Sincerely
From: Michael Gibson
7 Nov   [#10] In reply to [#9]
Hi Elang, I took a look at this a bit more today and there's kind of a complication.

If it's set up as "angle turning to the left or right", that would mean a turn of 0 would just keep going in the same direction as the previous line, right?

But your figure you posted above is not measured using that, it uses the opposite direction.

For example your figure measures 67 degrees like this:



As the angle decreases, point C comes closer to point A with segment BC. With an angle of 0 you'd have line BC going in the opposite direction from AB, right?

But specifying the amount of turn to the left or right would be like this instead, wouldn't it? :



- Michael

Image Attachments:
TurnToRight1.png  TurnToRight2.png 


From: Elang
7 Nov   [#11] In reply to [#10]
Hi, Michael... yes indeed!

Actually what I did was put 270+67 in the '<' tab to achieve the exercise. First, I checked if I put the end-point 'right below' then what is the '<' stated. Turns out that it was (and always) 270, so I add it with 67 to achieve the same result. However, 'the snap' would also includes snap to X Axis.

Maybe, to achieve the same result we can put like "65r_67" ? ( @_@; )
The '_' goes for 180-x degrees... so '_67' = '180-67' ?

I don't know which way is better, to be honest....
From: pressure (PEER)
7 Nov   [#12] In reply to [#10]
Would adding 4 snap lines resolve the ambiguity of r67? Say the black line is the prior segment and magenta is the snaps:



- Peer

Image Attachments:
relative angle.png 


From: MO (MO_TE)
7 Nov   [#13] In reply to [#10]
Hi
Maybe it makes more sense to use "clockwise" and "counterclockwise" definitions instead of left or right.

E.G. c99 or cc99

c0, cc0, c360 and cc360 will be on the last polyline segment, And c180 or cc180 will be along the last polyline segment.
From: Michael Gibson
7 Nov   [#14] In reply to [#12]
Hi Peer,

re:
> Would adding 4 snap lines resolve the ambiguity of r67?

It could for picking with the mouse but not for controlling it by text input alone.

- Michael
From: Michael Gibson
7 Nov   [#15] In reply to [#13]
@MO,

re:
> Maybe it makes more sense to use "clockwise" and "counterclockwise" definitions instead of left or right.

Maybe it's not so bad for left and right to mean make the point on the left or right hand side but it doesn't necessarily also have to be a "directional turn angle".

- Michael

Show messages: All  1-6  7-15