> One thing I will change is where the fonts should be located. When > they are included in the same directory as the Plucker documents > it will be a very slow process to find the fonts if you have a lot > of documents in the directory (that's why we added an option to not > check the card every time we sync the document list). The first time > I started the viewer on my TRGpro (1000 Plucker documents on the CF > card) I got a blank screen for a very long time while the VFSfont > code was scanning the Plucker documents trying to find font files.
I should note that if the vfs font code were working like it should (and like it will after the optimizations I suggested), it wouldn't have done a vfs font scan at startup unless a vfs font was being used to show the library or the current document, and that vfs font was moved or deleted. Normally, the vfs font scan is done only when doing a vfs doc scan or when popping up the font dialog if this wasn't already done. But I agree about your change--it would be good. However, I would really like LAUNCHER to continue working. I suspect that there are users who pop everything in there. Alex _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
