Thread: [pilot-db-list] Re: pilot-db current CVS version

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

On Mon, Feb 23, 2004 at 11:51:28AM +0000, Mark Walker  wrote:
> Thanks for sending the CVS file.  Where do you want bug reports to
> go, to you, to the bug list, or to the discussion list?  

I haven't thought about it yet.  My guess is that it's probably best
to send bug reports to the list if they are some large problem we need
to work on real soon, and to the bug tracker if they are something
that we want to remember to get back to later.  Both wouldn't hurt.
I'm posting this reply to the list so we can follow up there.

> The compile claims to have Sony Hi-Res, but it does not work.  I was
> also sent a copy of the stable version recompiled (by you?) to
> simply remove the large db msg.  It also does not work as hi-res.

For right now, it's going to be important to differentiate between the
bugs in the stable version and the bugs in the CVS version.  Sad as it
seems, the CVS version is currently an entirely unknown quantity: it
might fix some bugs, or it might introduce a lot of new ones.
Depending on which is the case, we'll either ditch the CVS version and
rollback, or start fixing the bugs in the CVS version.

> The plug-in button on the database view does not work, although
> plug-in support is compiled in (also stable recompile).  Plug-ins
> appear to work via the menu, but causes a reset (Memo-Export, Report
> and Information).  Interestingly, when I tried Report on a
> non-reportable database (i.e., no integers or floating point fields)
> it worked, but when I switched to a Reportable db it required a soft
> reset (button still worked, so no freeze).
>
> The plug-in menu item on the db list view does not appear to work.
> The only one that you should see a result from is colorselect, and
> instead of offering colours, it gives a debug msg; giving
> gridColorID and win Depth (also stable recompile).
>
> Any attempt to access Global Preferences from either view causes a
> non-frozen reset screen or on occasions a freeze requiring a pin
> reset.

Those sound major.  Are these with both versions, or only CVS?

> The above research was carried out on a Sony Clie SJ-33.  Maybe I
> will give prc-tools another try and see if I can get the code to
> compile.

I just started again with prc-tools a month ago, and found it to be a
lot better packaged than it was a couple years ago.  If you happen to
need Slackware packages, I've converted a number of the RPMs.

> PS, just remembered one possible answer to some problems, the file
> sizes are approx CVS:160k and stable recompile:150k, yet the offical
> realease is 170k, has color, hi-res etc really been compiled in or
> is it just being reported as such?

Unknown.  I went with the default configure options, but I haven't
tracked down what actually happened.  As a discouraging note, I've
been finding obviously non-compilable typos in some of the less used
code paths, so my faith in what "compiled in" means is scant.

> Best wishes.
> 
> Mark
> ----- Original Message -----
> From: Nathan Kurz <na...@ve...>
> Date: Sat, 21 Feb 2004 13:22:40 -0700
> To: mar...@op...
> Subject: pilot-db current CVS version
> 
> > > While we are waiting for the new release if anyone wants to send the
> > > debug msg recompiled version to me it would be much appreciated.  At
> > > markwalkeratoperamail.com
> > 
> > Here's a copy of the CVS version, which is probably going to have more
> > bugs than the current stable version---although it doens't appear to
> > have the problem with the debug message about large databases.
> > 
> > Likely we'll try to make two small releases in the short future:  one
> > a small bug fix version of the current stable version, and one alpha
> > release based on this new version.
> > 
> > So trying out this version so we can catch the obvious bugs before a
> > more general release would be a fine service.
> > 
> > --nate
> > 
> << db-en.prc >>
> 
> 
> 
> Mark Walker