Menu
▾
▴
#20 1.19B.31: Create RDIM confused by rel+on, "+end, etc.
Tested only on 1.19B.31
Depending on how the initial options are set, the process for adding a radius dimension can fail, or lead the user to produce unintended results. Prompts are still unclear depending on the initial options too.
I think the menus ought to provide the user with generally-expected results. If they want something strange, like having the radius pointer not be on the arc it refers to, they should perhaps have to do this manually via the editor.
Perhaps the part where the user selects the arc ought to ignore the settings and assume the user means the pointer to be on the arc. Currently, having the settings on "End", "On", "Relative + On", etc. can produce unanticipated prompt sequences, and strange results.
As a rule I always set everything up to be positioned dynamically if necessary, because some of my models may vary wildly with different input. I figure for a parametric model, everything ought to be parametric.
Scenarios:
Refer to attached test file.
The arc is arc_fil(#12,#5, #3, 30, 4)
-------------------------------
1. Initial settings: End.
User: Create, Dimension, Radius
Prompt: Select arc
User: <selects arc>
Prompt: Enter Break Position
User: <selects "Relative" + "End"; chooses the same arc: (assumption: the text will be relative to the actual arc, even if it changes position.)
Prompt: Relative to what? Choose base position !
User: <selects same arc>
-Nothing happens-
Instead, user is re-prompted to choose base position
Prompt: Relative to what? Choose base position !
-If user chooses, he is actually selecting a position for the radius pointer relative to the arc. Not usually what is wanted.
User: <goes along with the gag, and selects same arc>
Menus appear for position along arc, and for relative distance, then finish with the radius pointer pointing to the right, some distance away from the arc. BAD
MBS code looks like this:
rdim(#13,#12, startp(#12) + vec(30, 30), startp(#12) + vec(30, 30));
-----------------------------------------
2.1. Initial settings: On.
User: Create, Dimension, Radius
Prompt: Select arc
User: <selects arc>
Prompt: Enter Break Position
User: <selects "Relative" + "On"; chooses the same arc
Prompt: Relative to what? Choose base position !
User: <selects same arc>
-Nothing happens-
Instead, user is re-prompted to choose base position
Prompt: Relative to what? Choose base position !
-If user chooses, he is actually selecting a position for the radius pointer relative to the arc. Not usually what is wanted.
User: <goes along with the gag, and selects same arc>
Menus appear for position along arc, and for relative distance, then finish with the radius pointer pointing opposite the arc at the specified relative distance away. BAD
MBS code looks like this:
rdim(#18,#12, on(#12, 0.5) + vec(30, 30), on(#12, 0.5) + vec(30, 30));
--------------------------------------------------------
What ought to happen:
User: Create, Dimension, Radius
Prompt: Select arc
User: <selects arc>
Prompt: Enter Break Position
User: <selects "Relative" + "On", or "Relative+End", or whatever; chooses the same arc
Prompt: Relative to what? Choose break position !
User: <selects same arc>
Menus appears for relative distance,
Prompt: Choose end position relative to breakpoint ! (shows marker for breakpoint.)
User: <selects marker>
Menus appears for relative distance,
finish with radius pointer on arc, with breakpoint and end as specified.
Logged In: YES
user_id=1860753
Originator: NO
I'm not quite sure if this bug report is still
valid. I have a feelning that the logic around
relative positions has changed. Please let me
know if you still feel that there is a problem
with RDIM.
Logged In: YES
user_id=739930
Originator: YES
The function now works correctly. Menu prompts still unclear, but that's a different bug. :-)