Backup behavior on "new databases"

[Dan Mick <dmick@xxxxxxxxxxxxxxxxxxx>]

Warning: I haven't tested this yet, but Bharat agrees it looks right.
The instructions are for version 1.009-BETA-4 only (although they
should adapt to other versions):

I'm disappointed that Backup doesn't back everything currently on my 
Pilot up at all times; I lost several new databases when my Pilot
crashed because I hadn't revisited the Backup configuration screen
after having installed the new databases.  (You have to select the new
databases as "active" because Backup doesn't do it automagically;
it knows about the new databases, but they're made "inactive", so
don't get transferred.)

Well, that's easily fixed; if you prefer the "back it all up" behavior,
you can get new databases to automatically become active backup 
candidates, by changing line 375 of Backup.pm as follows:

At line 375 in Backup.pm, change 
	push(@{$PREFS->{"inactive"}}, $db);
to
	push(@{$PREFS->{"active"}}, $db);
	
Happy backing up.

---------------------------------------------------------------------
********************************************
*   PLEASE DO NOT POST PILOTMANAGER BUGS   *
*  TO THIS ALIAS.  SUBMIT BUG REPORTS VIA  *
*     THE FEEDBACK MENU IN PILOTMANAGER    *
*             --------------------         *
*      This is a public mailing list!      *
*  Please do not publish Sun proprietary   *
*            information here!             *
********************************************