My thought is to add to the title bar for each run a generic text field to
be read from the ini file for each run. Geez! could then store
Time/Date/Event information there, and we could see it at the top of each
window. This could be done in the current 3.1 environment, and may work as
well as long file names, especially if we can store to different
directories...
Rick
> -----Original Message-----
> From: Brian Meyer [SMTP:bm@gte.net]
> Sent: Tuesday, August 31, 1999 10:35 PM
> To: geez@autox.team.net
> Subject: Wish list items
>
> I thought I'd start a list of things we'd like to see added to or changed
> in
> future releases of GEEZ! As if Byron didn't have enough to do already,
> this
> should keep him busy for the next year or so. :-)
>
> I'd like to see an "Apply" button on the map adjustment dialogue so it
> doesn't close the box when you want to try an adjustment. This is actually
> the idea of a friend of mine (he supplies the car, I supply the GEEZ!). We
> almost never get the map adjustments right on the first try.
>
> Long filenames: Even though I understand that GEEZ! is written to run on
> old
> clunky Win3.1 laptops that many of us would rather use at the events then
> the new Pentium Win9X notebooks, I'd like to see support for long
> filenames.
> Perhaps as an option during the installation we could specify which
> operating system we will be using it on.
>
> It may be difficult to implement, but I'd like to see an app for the Palm
> that allows you to input the "Race Diary" information used in GEEZ!. After
> the runs are compete, you could enter the data and somehow attach it to
> the
> recorded file, and both would get downloaded into GEEZ! later.
>
> Ideas also mentioned on the list so far:
>
> Add the ability to specify which directory downloaded files go into. Add
> the
> ability to create that directory (in GEEZ!) if it doesn't yet exist.
>
> Time stamp on the file names. (Requires long filename support)
>
> Make the calibration process more clear by adding "Left side UP" to the
> prompt. Perhaps add a 'sanity check' to the program to show an error
> message
> if the G-Cube is 180 degrees off during calibration.
>
> Add a check for the battery voltage level in the power supply and a
> warning
> if it falls below a certain threshold (6 volts).
>
> That's all I can come up with for now. Feel free to add anything you would
> like to see.
>
> -Brian Meyer
> Add a "Daddio" smoothing algorithm so my runs will at least look faster
> then
> I really am...
>
|