Click to Launch
(workaround): repainting enabled go pause clear buttons.
under earlier JDK 1.4.1_01
FrameSetup failure (max extent not respected).
bar graph backgrounds.
water drop graphics for firedog
force arrow size
force arrows with mouse.
bag is now sorted by mass.
play area’s ‘reset’ to ‘clear’
ramp so that model continues even after time is up, but no more data is
velocity readout under the time readout.
in-graph readouts ignore the mouse (were obscuring mouse clicks from
graph readouts have shadows now.
vertical units label, since duplicated on readouts.
time ticks to y=0 axis.
bracket for y-axis ticks & labels.
data recording time to 30 seconds.
- Striped Arrow coordinate view stripes
for perp & parallel?
- My technique will be difficult for
perp & parallel. We shall confer about
the Cartesian arrow graphics before pursuing.
- The height readout of the ramp’s end
doesn’t respect the zero-point potential energy height level.
- Convert layout code to size-agnostic
- Refactor RampLookAndFeel to be field
- Rename 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.
- Some other object (not a brick wall)
at the top of the ramp?
- Someone else suggested this, I think
a brick wall is fine.
- Block incorrectly
curves around a 90 degree angle.
- Should we ignore this?
- Or restrict the angle
of the ramp?
- Or implement correct
- Performance Enhancement.
- How to render images
at high resolution at view scale = 1.0?
- Test at lower resolution.
- Wiggle me to drag the ramp (2nd
- Add help.
- Water splash should hit
- Running over the man
with the block should squash him.
- Reduce overlapping of force vector
The ramp overheats
After playing with this for
awhile, I’m convinced that the Applied force slider should be in the
rather than in the play area. It’s not a
control that’s attached to an object.
The man is very easy to move.
Right now it’s almost
impossible to see what’s happening on the graphs when all three are
Should we try to alleviate this?
Or should we optimize for 2 maximized graphs at once?
The lines and axis labels
appear fuzzy on the edges but are clean on moving man. Is this an easy
Not at present.
I’ll better be able to address this when I know what screen
you were running at (I presume 1280x1024).