On Wed, Mar 13, 2002 at 09:20:21AM -0500, Reiner Schulz wrote: > (1) in the current version of the viewer, using the jog-dial of my sony > clie t-415 causes the viewed page to be scrolled by increments of 1 point > which frankly isn't very useful. did i miss a preference setting which > changes that behavior to, for example, scrolling by 1 page/line?
With JogAssist enabled, it tries to emulate a scrollbar up and down arrow click for every up/down move on the JogDial itself. Currently I'm working on an extra branch of the code to add in native jogdial support into plucker, including the ability to configure the buttons. If you want to download a pre-testing build of plucker, you can get it from http://www.array.org/~adamm/plucker-sony/20020308/viewer_en.prc This will create a new plucker icon called Plucker-sony, it won't over-write any plucker docs or existing program. You can configure the JogDial from Options -> JogDial Actions... while viewing a doc. Since I havn't had the chance to add in proper support for systems with JogAssist turned on, I would recommend that you turn it off for this instance of Plucker, alteast to test out the new features. As well, on the Library screen, the JogDial should work there as well, atleast in highlighting documents and opening them. (Back doesn't work yet, but according to UI specs it should close down the app since we can't go any futurther back within plucker) > (2) it's a question of taste, but i don't like to use the stylus for > navigation, in particular to follow a link by tapping it. are there people > who would agree that using, for example, the jog-dial to select and follow > a link on the currently displayed page is convenient? turning the jog-dial > would rotate through the links where the currently selected link is > highlighted/marked by, for example, white-on-black inversion. pushing the > jog-dial in would follow the currently selected link. > together w/ the already implemented function-to-button assignment that > would make the stylus superfluous, at least for reading and navigation. That was my initial goal as well. The trouble is how the documents are stored and recalled from RAM poses some chicken-and-the-egg problems. Specifically, how are we supposed to find out whats next, if we don't even know what's coming up, but we don't know whats coming up without actually displaying it. (Correct me if I'm wrong, this was my intrepretation of the display). My understanding is that this method will change within the near future which, hopefully, will allow for easy support of that feature. It would be nice to be able to use the JogDial for complete (basic) navigiation, but still be able to fall back on the traditional stylus method ofcourse. BTW, hires support for the Clie is coming soon too :) -- Adam McDaniel Array Networks Calgary, AB, Canada
