TheRamp v0r13, that is to say, 0.13
Click to Launch
New in this
man halfway along path, so he is not camouflaged by the wall.
module starts with Force graph maximized.
graph contains a graph slider.
& block change color when friction is high (single discrete change)
or coname Applied Force to Push or Man or Applied (push) or something
like that. I don’t think students will
easily make the connection between applied and the push?
other object (not a brick wall) at the top of the ramp?
else suggested this, I think a brick wall is fine.
incorrectly curves around a 90 degree angle.
we ignore this?
restrict the angle of the ramp?
implement correct crash physics?
sizes are locked on moving man—should we fix the button sizes here as
now it’s almost impossible to see what’s happening on the graphs when
all three are displayed. Should
we try to alleviate this? Or should we
optimize for (at most) 2 maximized graphs at once?
switching objects clear friction? Should
it clear the graphs?
Arrow coordinate view stripes for perp & parallel?
technique will be difficult for perp & parallel.
We shall confer about the Cartesian arrow graphics before
layout code to size-agnostic (not hard-coded).
splash should hit the block.
overlapping of force vector labels.
lines and axis labels appear fuzzy on the edges but are clean on moving
man. This seems to be related to the resize mechanism we’re using here
(different from moving man.)
RampLookAndFeel to be field of RampPanel?
- Test at
me to drag the ramp (2nd panel only).
to render images at high resolution at view scale = 1.0?