> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of David A. > Desrosiers > Sent: Sunday, March 09, 2003 6:13 PM > To: [EMAIL PROTECTED] > Subject: Re: Deleting documents while set to Manual update > > > Sounds alot like CodeBase :) That's all we need, DBF > > support in plucker ;) > > Even simpler. If you're in the doclist, and delete a > document, and your document preferences are set to "Manual > Update", strikeout the title of the document, or change the > icon to 'N/A' or something for "offline" docs sitting in > another SD/CF/whatever card that isn't currently in the Palm.
If you do a delete from the document list _within_ the viewer, no need: the doc list update is done regardless of how your update prefrence is set. The original case was what happens when you delete a Plucker doc _outside_ of the viewer, like using a USB card reader to delete the underlying document file from /Palm/Programs/Plucker. If your preferences are set to Manual Update, the doc list still shows the document, because Plucker hasn't been made aware it's gone. That's as expected. If you try to open the document, you get an error because the document doesn't exist to open. If you try to delete the document, you get the same error, because the document doesn't exist to delete. My suggestion was that if you tried to delete a document from the list, and the delete failed because the document wasn't there, removing the entry from the doc list was a reasonable action for the viewer to take. Mike disagreed with me. My interest was speed. When you have a lot of Plucker docs on a card (I have 48MB worth), a manual update takes time. I find it a lot faster to add/remove files with a USB reader rather than hotsync/move and delete on the device. Adds of course require a full update. Deletes would be simpler if it were possible to simply delete the doclist entries for files you have removed outside the viewer. On those lines, a possible feature request: I keep all my Plucker docs on a CF card, but the viewer handles them equally well on card or in RAM. My launcher (LauncherX) is VFS aware, and offers three choices for how it handles updates: Automatic: apps are rescanned each time the launcher is activated Manual Update: apps are only rescanned when explicitly requested Ignore card: apps are rescanned automatically, but only in RAM. Expansion cards are ignored. The third option -- having the viewer only look for new docs in RAM -- might be a nice addition. > d. ______ Dennis _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
