#3017 BLOC Trial-3: UI for Measure Activity that has the standard toolbar as UI
Zarro Boogs per Child
bugtracker at laptop.org
Tue Sep 11 09:34:47 EDT 2007
#3017: UI for Measure Activity that has the standard toolbar as UI
-------------------------------+--------------------------------------------
Reporter: arjs | Owner: arjs
Type: enhancement | Status: new
Priority: blocker | Milestone: Trial-3
Component: measure-activity | Version:
Resolution: | Keywords: ui, icons
Verified: 0 |
-------------------------------+--------------------------------------------
Comment(by arjs):
> There are really two dimensions to this, high pass value and low pass
value. Maybe just enumerate things as thirds:
>
> {{{
> a. high freq
> b. high and mid freq
> c. low freq
> d. low and mid freq
> e. everything
> f. mid freq (maybe)
> }}}
>
To clarify, these settings aren't aren't Band Pass, Low Pass and High Pass
Filter. This setting is like the 'time base' control on oscilloscopes. It
essentially helps one fit the waveform on the screen according to the
appropriate frequency. For example if one isnt able to fit the complete
waveform on the screen, means one need to select a larger time base etc...
Very technically, if we want to call this a filter, IMHO it would be a low
pass filter with increasing cutoff frequency as the slider frequency.
> One second between samples, between display pixels, or between grid
lines? About 2 to 6 seconds across the width of the display seems good.
>
One second means one second interval between every two samples that are
recorded. Each sample is one value. These logging features are generally
useful when one has connected say a temperature sensor and one wants to
record the temperature variations over a day at an interval of one hour
(in these we will select the 1 hour logging interval)
> This is taking lots of space that could go to the graph. Automatic range
adjustment could reduce the need for the slider. (can't entirely eliminate
it though)
>
I had thought about it earlier (having automatic range adjustment, much
like 'autoset' we have in modern oscilloscopes) However I believe that
such a feature takes out half the learning from the process (and also half
the fun).
>
> Making this bigger would be good. Reducing the other stuff on the screen
would help. There could be a way to make the graph full-screen.
>
Response time has been found to drastically deteriorate with larger
drawing area. I wouldn't mind help in optimizing code to improve response
time.
--
Ticket URL: <https://dev.laptop.org/ticket/3017#comment:13>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list