Re: strike-thru in libraryform
Michael Nordstrom [EMAIL PROTECTED] wrote: On Mon, Jun 02, 2003, Alexander R. Pruss wrote: I assume you can turn this off? ARP Yes, and it is off by default. Argh! Another option! Why not use bold in the library to indicate unread documents instead? MJR ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
adding options (was Re: strike-thru in libraryform)
By the way, when new options get added, are people trying to keep the prefs backwards compatible, and if so, how? (When I added the multiple term search and transliteration search options, I used bitfields of an existing pref item, the case-free search one.) Alex -- Dr. Alexander R. Pruss || e-mail: [EMAIL PROTECTED] Philosophy Department || online papers and home page: Georgetown University || www.georgetown.edu/faculty/ap85 Washington, DC 20057|| U.S.A. || - Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur. - Paul of Worczyn (1424) ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: strike-thru in libraryform
On Mon, Jun 02, 2003, MJ Ray wrote: Argh! Another option! Well, the other option is that I decide how everything should look and work. Personally, I think it is better to leave some of those decisions to the user ;-) Why not use bold in the library to indicate unread documents instead? That's a very good suggestion. We would have to remove the option to use a bold font for the library, but I guess it should be enough to be able to select narrow, normal, or large. Still, considering the amount of code we are talking about (a few lines) we could even make it possible for the user to select whether the strike-through or bold font should be used for read documents. However, since Matto wrote the code I will leave the decision up to him whether the strike-through should be replaced by a bold font or if they should both be included. /Mike ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: strike-thru in libraryform
Still, considering the amount of code we are talking about (a few lines) we could even make it possible for the user to select whether the strike-through or bold font should be used for read documents. Or, more precisely, whether strike-through should be used for read documents, or bold for unread ones. (Or both, I suppose. Two checkboxes will do it.) Alex ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: strike-thru in libraryform
On Mon, Jun 02, 2003 at 10:36:43AM +0900, masakazu wrote: I added a new feature in library form to indicate which document is read or unread by strike-thru lines. You can also delete read document at a time from menu. Changes are already reflected to CVS. Aw Crap! .. Your latest commit causes a crash in all OS5 devices whenever I try to open a document! :( Actually.. I think its related to the ErrTry/ErrCatch bug in PACE that we discussed earlier. Infact, in your case its being caused by similar circumstances: Within StoreReadTimeInDocumentList() you embed FindDocData() within an ErrTry. It's that same scenario which subsequently requires me to force all OS5 users to display the document library on startup. Oh well, I'll find a fix for my side. You need not worry about it, Matto. -- Adam McDaniel Array.org Calgary, AB, Canada ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
autoscroll speed control
use whatever controls are assigned to page-up/down or half-page-up/down when autoscroll is active. That sounds like a good default to me. Another thing you might consider is to allow the autoscrolling method introduced in the doc reader ReadThemAll: the text remains stationary and a horizontal line passes gradually down the screen to reveal the next page. ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: strike-thru in libraryform
On 2003.Jun.3, at 07:31 AM, Adam McDaniel wrote: On Mon, Jun 02, 2003 at 10:36:43AM +0900, masakazu wrote: Oh well, I'll find a fix for my side. You need not worry about it, Matto. Thank you. I copied and pasted StroeCategoriesInDocumentList to make StoreReadTimeInDocumentList. Please check both. matto ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: strike-thru in libraryform
On Tue, Jun 03, 2003 at 10:10:27AM +0900, masakazu wrote: On 2003.Jun.3, at 07:31 AM, Adam McDaniel wrote: Oh well, I'll find a fix for my side. You need not worry about it, Matto. Thank you. I copied and pasted StroeCategoriesInDocumentList to make StoreReadTimeInDocumentList. Please check both. I think I have the problem fixed. I just sent a patch off to Mike, awaiting his blessing. There wasn't anything that you did wrong, it just so happened that the current method of calling FindDocData() also caused a crash in OS5. All is fixed and should be commited soon. -- Adam McDaniel Array.org Calgary, AB, Canada ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
