> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of David A. > Desrosiers > Sent: Saturday, February 08, 2003 12:33 PM > To: [EMAIL PROTECTED] > Subject: Re: Plucker bug or problem on my device? > > > As a suggestion for a future release, it would be nice if a Delete > > operation would simply remove the document entry if the underlying > > document didn't exist, rhather than leaving a stray pointer > > to nothing lying around. > > Wouldn't this require Plucker to scan your RAM, ROM, > and card(s) at startup to determine that, thus removing the > feature you've set to "Manual"? It used to do this in fact, > but now no longer does, due to long scan times.
I recall the old behavior, and was grateful for the manual refresh option, precisely because of the long scan times. But see below. > > Meanwhile, does anyone have an idea of what might be going > > on here? I'm about at the point of doing a hard reset on > > the Visor, and redoing everything from scratch to try to > > clear up the problem. > > That might work also, but I suspect that since you deleted the doc > outside of Plucker, it doesn't know it is missing, and since you didn't > do a refresh, all of the pointers are messed up, and Plucker believes the > document exists when it doesn't, when you try to move it or file it. I _did_ do a refresh. That's when the library pointers got hosed and duplicates of all document entries in categories appeared in Unfiled. The possible bug I'm complaining about is that Plucker is crashing and corrupting the document list on an Update Documents operation. If I remove a Plucker document outside of Plucker, and do an Update Documents operation to correct Plucker's document listing, Plucker crashes. When I reset the device and reload Plucker, the document listing is corrupted, and I must remove plkrdoclist and redo it from scratch. Also, when I add new documents to the Plucker directory on the card, and do an Update Documents, Plucker crashes, corrupting the document list. If I remove plkrdoclist, invoke Plucker, and do an Update Documents operation, Plucker crashes, but when I reset and re-invoke, all of the documents are in the Unfiled category and may be reclassified. What I'm asking is "Why is Plucker crashing on an Update Documents operation?" I call it a possible bug because I don't know if it's a problem with Plucker itself, or is a side-effect of something screwy on my Visor. The latter case is why I'm tempted to do a hard reset and redo everything from scratch. > It all seems logical to me, but then again, for Plucker > to "fix" the pointer to the doc, it would have to scan the card(s) > and find out if the ref to the doc in the library list actually > exists on the device, before moving it. Then you're back to square > one again, long scanning times. Perhaps I'm missing something here. I remove a document outside of Plucker. The underlying document no longer exists, but Plucker still has the entry for it in the library form. Selecting the document and choosing Delete returns an error message, because the underlying document isn't there. Why is removing the document entry from the library listing an inappropriate response to that condition? > d. ______ Dennis _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
