On Sunday, Sep 22, 2002, at 15:34 US/Pacific, David W. Fenton wrote: > The PAGE DOWN key doesn't move the cursor! All it does is drive the > scrollbar, and this is one of the reasons why I was having so much > difficulty losing my place in the EDIT LYRICS window.
> Is this the same on the Mac? That depends. Text editors like CodeWarrior, BBEdit, and Alpha don't do that by default because they observe some long standing conventions about document navigation keys. You can change the default bindings though. My Text Editor plugin uses these conventions as well and they are listed in the PDF documentation for Text Editor on my site in case you'd like to read up on them. The behavior you describe is standardly attained by Option-DownArrow or Option-UpArrow key combos whereas PageUp and PageDown keys only change the view (not the selection). CodeWarrior has outstanding "partial word" navigation/selection features invoked by Control-Arrow/Control-Shift-Arrow. However, on MacOS X, the Cocoa frameworks based applications don't observe the Option-Arrow convention and it's driving quite a few of us nuts because the customization process is hideous. This is one area where the NeXT bullies have been especially recalcitrant about changing their ways. Applications like word processors and spread sheets may have slightly different conventions. I haven't used M$ Word for years but I think it has defaults like you expect. I'd have to say though (since my first word processor was M$ Word), that using the Command/Option/Shift-ArrowKey conventions are more motion efficient and thus the faster. Philip Aker http://www.aker.ca _______________________________________________ Finale mailing list [EMAIL PROTECTED] http://mail.shsu.edu/mailman/listinfo/finale
