Framemaker 11, Windows 7, scrolling to next page with touchpad

[ggbusta]

Greetings.

Not sure this question belongs here.  If it belongs elswhere please let me know.

When I try to select a bulleted list that continues onto the next page my selection automatically leaps forward far beyond where I want it to stop (like the end of the document sometimes).

I've tweaked every Windows 7 touchpad and mouse parm I can find to no avail.

I've Googled this with no luck - lots of hits all of which address slowing down the mouse but only a few address the touchpad but still met with no success.

Anyone have ideas? 

Again.  If this is in the wrong forum please let me know.

Thanks,

Jerry

[Arnis Gubins]

This is a tough one and more of an operating system level question. From what I know, FM doesn't have any specific support for touchpads (gestures) and relies on the OS for the correct info. From what I've seen, manufacturers tend to implement touchpad behaviours in their own way and use different brands of touchpads. What works for adjusting a Dell may not work for an HP or Lenovo, as well what works on a Synaptics device may not work as well on Elan on, etc.

Check to see that your touchpad drivers are up to date. If those don't help, then you might look around for third-party alternate drivers for your touchpad device.

[ggbusta]

Thanks alot Arnis.  I'll look into 3rd party drivers.

Jerry

[Lynne A. Price]

Jerry,

    I don't understand what you are seeing. Is the problem that you try to select something and wind up with a much larger selection than intended? If so, the behavior could indeed involve your touchpad. However, since you've written to the structured FM forum, I suspect your document is structured. In this case, you might simply be seeing the way selections work in structured documents.

   In particular, FM automatically "heats" (expands) a selection that includes one boundary of an element to include the entire element. For example, if you turn on the View Element Boundaries option and drag over one of the resulting square brackets, FM selects that entire element. (Note that it is possible to select the beginning of an element's content without selecting all the content or the element itself.)

   The reason for this behavior is that anything that can be selected can be deleted, and it doesn't make sense to delete one boundary without the other. As another example, suppose you have a Title element followed by a Paragraph. If you click in the middle of the Title and shift-click in the middle of the Paragraph, the selection heads to include the entirety of both elements. Without this expansion, it would be possible to delete the end of the Title and the beginning of the Paragraph leaving both elements malformed. If one of the elements is large, for example, a Section or List that spans numerous pages, you can unexpectedly select a large portion of the document.

  In XML terms, if you select a start- or end-tag, FM selects the entire element. Thus, FM structured documents are always well-formed.

    --Lynne

[ggbusta]

Thanks Lynne.

Your reply is very educational and yes, I am using structured.  I am a new user of FM and need to further digest what you wrote.  Thank you very much for taking the time to respond so thoroughly.

Jerry