RE: Autoscroll MarkII
> Great work. I had to fix a minor bug in the viewer.rcp.in file or > it wouldn't compile (the PUSHBUTTON had a NOFRAME option that can't > be used for these buttons --- maybe it should be DISABLED, too). Whoops, forgot about that stray NOFRAME, thanks for catching that. DISABLED is a good idea, I left it off just since that what the PalmOS time set popup does, but there isn't any real need to be able to click on these ones. Disabled it is. > Another thing (that I won't fix:) is that the new strings should > be added to a *all* language files. Will do. For the translations of languages I don't know (almost all of them), is it recommended that I just write the english in, for that language maintainer to append? Or consult babelfish? > I don't think the narrow fixed font should be available in the > Preference form (it should only be used for the text). That one wasn't really a conscious decision--just an artifact that this is from an earlier version of the current version in the trunk that has tag working instead of just a drop-down option. But just as a question, is there a particular reason that you don't recommend a fixed width as an option, since it's already been pretty well paid for in terms in terms of the font resource? Most people I know prefer to read their email in constant width text, even though could also read in a variable width font. > BTW, before this code is merged with the main trunk a description > of the autoscroll feature should be added to the documentation. > We might have to think about a way to remove the autoscroll control > (and also other controls) from the toolbar. As you can see the toolbar > is quite crowded at the moment, so it will not be possible to add any > other controls to it. Maybe it should be possible to "configure" the > toolbar, i.e. be able to choose what controls that should be included. > Some of the controls (e.g. back, home, forward) could always be > included while other controls would be optional. Certainly a fair thing if there is many more buttons coming in that would be tapped often enough to warrant not having to go to the menu each time. Right now, I can testify first hand that there is no room left for a new button, after many hours of both the b&w and colour icons. If there is something new that comes up that needs toolbar real estate, I would probably most recommend sacking the +, - buttons and using those pixels for the incumbent button. A toolbar selector option would be a handy feature (a list of checkboxes of controls to display--this is the route that CSpotRun takes?). I agree that a toolbar manager is probably a better solution than just hiding the autoscroll since there is no net gain really of just hiding it (leaves a hole in the middle of the toolbar that can't be used for anything else), and if things are to slide over and replace it, on the way to a toolbar manager already. Best wishes, Robert
RE: Autoscroll MarkII
Dirk brought up a good point that most people might not know what a 'tick' is. Though it is explained in the 'tips' file of the form, a better UI is not to have to have people looking in the docs for what things do. Will change as you suggest, to seconds or milliseconds. Best wishes, Robert > "MJ" == MJ Ray <[EMAIL PROTECTED]> writes: > > >> The other thing. In settings you could set the Autoscroll delay in > >> "Ticks", i guess many users with no programing experience are confused > >> by the "Ticks". Maybe give this setting in seconds a better? > > MJ> Do Ticks vary between machines? > > Don't know, but AFAIK there are SysTicksPerSecond() that should give > the right value. > > cu, > Dirk > > -- > Permanent URLs to the latest Version (1.1.11) of the Plucker > Windows installer > - For the Webpage: http://www.dirk-heiser.de/plucker > - Direct Download: http://www.dirk-heiser.de/plucker/plucker.exe [2.94MB] >
RE: Autoscroll MarkII
> Should there be a (configurable) pause before automatically > traversing the link? If the page autoscrolls to the bottom (or > to the place where the link is in the doc) and then goes right to > the next page, I might not have read the last couple of lines > before the next page appears. Something to consider. Sounds pretty fair, and also for the link click (latter, if can do something in a small amount of code). Will keep this pause-on-next-page idea handy for the time when tour support is being worked on. Best wishes, Robert
Re: Autoscroll MarkII
On Wed, Aug 08, 2001, Robert O'Connor wrote: > A second (hopefully near the final) draft of autoscroll is available. Great work. I had to fix a minor bug in the viewer.rcp.in file or it wouldn't compile (the PUSHBUTTON had a NOFRAME option that can't be used for these buttons --- maybe it should be DISABLED, too). Another thing (that I won't fix:) is that the new strings should be added to a *all* language files. I don't think the narrow fixed font should be available in the Preference form (it should only be used for the text). BTW, before this code is merged with the main trunk a description of the autoscroll feature should be added to the documentation. > -Bitmaps of (+) (-) widened for easier stylus tapping. We might have to think about a way to remove the autoscroll control (and also other controls) from the toolbar. As you can see the toolbar is quite crowded at the moment, so it will not be possible to add any other controls to it. Maybe it should be possible to "configure" the toolbar, i.e. be able to choose what controls that should be included. Some of the controls (e.g. back, home, forward) could always be included while other controls would be optional. Otherwise we have to make a decision about which controls that really are necessary to include in the toolbar. /Mike
Re: Autoscroll MarkII
"MJ" == MJ Ray <[EMAIL PROTECTED]> writes: >> The other thing. In settings you could set the Autoscroll delay in >> "Ticks", i guess many users with no programing experience are confused >> by the "Ticks". Maybe give this setting in seconds a better? MJ> Do Ticks vary between machines? Don't know, but AFAIK there are SysTicksPerSecond() that should give the right value. cu, Dirk -- Permanent URLs to the latest Version (1.1.11) of the Plucker Windows installer - For the Webpage: http://www.dirk-heiser.de/plucker - Direct Download: http://www.dirk-heiser.de/plucker/plucker.exe [2.94MB]
Re: Autoscroll MarkII
> Do Ticks vary between machines? They "Shouldn't(tm)" vary, but on different architectures, they're calculated differently, which results in a slightly different rate of precision (32-bit vs. 64-bit for example, and RISC vs. CISC). /d
Re: Autoscroll MarkII
Dirk Heiser <[EMAIL PROTECTED]> writes: > The first time i open the DB and see the new autoscroll control at > the toolbar i was a little bit confused. I expected that if i see the > run symbol (the right arrow) the autoscroll are on and if i see the > stop symbol (the filled black square) the autoscroll is off and taping > this button change the state. It depends whether you think of it as an indicator (showing the current state) or a control (showing the intended state). Showing the intended action is consistent with the other controls, I think. > The other thing. In settings you could set the Autoscroll delay in > "Ticks", i guess many users with no programing experience are confused > by the "Ticks". Maybe give this setting in seconds a better? Do Ticks vary between machines?
Re: Autoscroll MarkII
"Robert" == Robert O'Connor <[EMAIL PROTECTED]> writes: Robert> A second (hopefully near the final) draft of autoscroll is Robert> available. Code is in the plucker CVS under the auto_scroll Robert> branch for your inspection & bug fixes. This are the first time i try your autoscroll version and i wan't give you the feedback from my first use. At first, it seams to work fine so far i could see, only a few little cosmetic thinks. The first time i open the DB and see the new autoscroll control at the toolbar i was a little bit confused. I expected that if i see the run symbol (the right arrow) the autoscroll are on and if i see the stop symbol (the filled black square) the autoscroll is off and taping this button change the state. But the current implementation are inverse of this. This is not wrong, sure. It depend of the point of view. But IMHO this are not usual. Comments from others about this (maybe i'm the only one who think in this way :-)? The other thing. In settings you could set the Autoscroll delay in "Ticks", i guess many users with no programing experience are confused by the "Ticks". Maybe give this setting in seconds a better? Another thing not related to autoscoll: should the "Libary" menu entry move to the "Go" menu? I suggest: GO ViewOptions -- Libary Details<- or maybe move this to the view menu? -- Home Preferences Back Autoscroll Forward ---Button Action ...... cu, Dirk -- Permanent URLs to the latest Version (1.1.11) of the Plucker Windows installer - For the Webpage: http://www.dirk-heiser.de/plucker - Direct Download: http://www.dirk-heiser.de/plucker/plucker.exe [2.94MB]
Re: Autoscroll MarkII
DISCLAIMER: I haven't downloaded the prc to try it yet. These are just a couple suggestions based on what I read. Excellent stuff! >-Hitting top or bottom of a page (scrolling up or down respectively) stops >Autoscroll. If later add the tours, can add an if next page on the tour, go >to next page, else stop. Should there be a (configurable) pause before automatically traversing the link? If the page autoscrolls to the bottom (or to the place where the link is in the doc) and then goes right to the next page, I might not have read the last couple of lines before the next page appears. Something to consider. >Also not stop >autoscroll on a link click, to allow to navigate through a many-hyperlinked >text, and have it continue to scroll by--this one may need to get wired up A pause here might be nice too, but this time a pause after the link is clicked--to provide a line or two head start before the scrolling begins. clone "If one man is a clone, what is another?" Get 250 color business cards for FREE! http://businesscards.lycos.com/vp/fastpath/
Autoscroll MarkII
Hi Plucker Team, A second (hopefully near the final) draft of autoscroll is available. Code is in the plucker CVS under the auto_scroll branch for your inspection & bug fixes. A compiled .prc is also available at: http://www.rob.md/projects/plucker/2001_08_08/viewer_en.prc Intended behaviours running: -Ability to set autoscroll mode (pixel/page) [line later if available], as well as how much of a jump of each. Fractions have been cut from page options (eg 1/2 page) since redundant to either 80 pixels or 6 lines options, and can use less code. -Ability to specify either autoscroll up or down. -Start/stop/incr/decr autoscroll from appropriate toolbar GUI button, menu, or command stroke. -Start/stop/incr/decr autoscroll from hardkey, gesture, or screen tap. -Touching scrollbar, viewport (other than links), buttons, menu, command stroke or hardkey/gesture/screentap (that isn't a toggle/faster/slower autoscroll) should stop autoscroll. -HardkeyPowerOff/Autoshutoff stops Autoscroll. -When MainForm initializes (eg when launch app), set Autoscroll to off. -Hitting top or bottom of a page (scrolling up or down respectively) stops Autoscroll. If later add the tours, can add an if next page on the tour, go to next page, else stop. -Prevent any gestures/hardkeys actions from running when menu is displayed (otherwise will draw them to the menu window)...if mapped a 'toggle autoscroll', or 'go to top' to address button, then pressed it during a menu display, would cause it to draw into the menu. CSpotRun seems to suffer from this: if toggle when menu displayed, can see it autoscroll in the menu window. -When poweron, don't redraw the Autoscroll button to play if currently viewing a Large Image. -Stay on while autoscrolling should prevent an autoshutoff during scroll. -On options form, show alert when click the prevent autoshutoff during scroll tickbox. Only show the alert when checking the box, not unchecking it. Other notes: -Bitmaps of (+) (-) widened for easier stylus tapping. -Originally had the autoscroll in the main Preferences form. It was too crowded, and prevents any room for a future preference to be listed. Works better on own form. -Menu/button/gesture options changed from 'increase/decrease' to 'faster/slower' to make more clear that changing time interval, not jumpsize. -Code not added to stop scrolling on PageUp/Down Rocker key, since sort of useful to keep this maintained, so can jump down a page if currently autoscrolling some junk by, like an advertisement image. Also not stop autoscroll on a link click, to allow to navigate through a many-hyperlinked text, and have it continue to scroll by--this one may need to get wired up though, since unless scrolling by slowly, may be hard to have a pendown and penup in the hyperlink, before the hyperlink moves up out of its selection rectangle? -Original controls for setting jumpsize and interval were drop downs, but changed to spinners since smaller code needed, yet more flexible. -This is a not-yet-merged branch from about 2 weeks back, so Library, etc. may be a bit inconsistent with the current version, nor is preformatted text supported here. This gets fixed when merge the files. -There is a noticeable speed increase during single/double pixel scrolls if set colour depth down to 1. -Increase minimum delay up from 0 ticks, so that can't make it stutter (or else add a sentence warning that cranking speed up to 0 tick delay might do a stutter on certain hardware and a complex page). Noticed that CSpotRun only allows 5 ticks, not 0 ticks. ToDo: -LowBatteryDialog shutoff of autoscroll. Should be straightforward, just catch the vchr for low battery dialog in the HandleVChrs() along with HardwareKeys, and the rest. It is commented out in the source, however. For some reason, when it is uncommented as a case, it will cause autoscroll to stop running after about 20-30 secs or so. Don't know why. ToDo Perhaps: -Scrollbar arrow movement customization, ie allowing one to set how many pixels/lines/pages are scrolled when touch the arrows at the end of the side scrollbar. If can think of a way of doing this in a few lines, will drop this in. Would rather not have to look for the pen downs in the scrollbar arrow area. Rocker customization is straightforward, scrollbar arrow doesn't seem to be. Best wishes, Robert
