Hi All,
I have an annoying problem to do with the way the mouse wheel is utilised in 
FMP7
1. I want to use the mouse wheel to ONLY control the scrolling through 
records
    as this a fast method to do so
2. My layout design tends to be bigger than my screen area and so there are 
side
    and bottom scroll bars - that's normal
3. Sometimes the mouse wheel is "happy" to only scroll records (which is 
what I
    want) but sometimes it gets into the mode of scrolling L to R or Top to 
Bottom
4. At that point it will NOT scroll the records leaving the only way to do 
so is via the
    L/R slide bar in the LHS status window - which is cumbersome
5. The only to give record scrolling back to the mouse wheel is to exit and 
re-enter
    the data base
6. How can I lock the record scrolling to the mouse wheel and layout panning 
be
    left only to the side and bottom scroll bars regardless of the screen 
magnification

Best Regards Ron H. 

In article <xoH5e.4573$5F3.190@news-server.bigpond.net.au>, ronald_h70
@hotttmail.commm says...
> Hi All,
> I have an annoying problem to do with the way the mouse wheel is utilised in 
> FMP7
> 1. I want to use the mouse wheel to ONLY control the scrolling through 
> records
>     as this a fast method to do so
> 2. My layout design tends to be bigger than my screen area and so there are 
> side
>     and bottom scroll bars - that's normal
> 3. Sometimes the mouse wheel is "happy" to only scroll records (which is 
> what I
>     want) but sometimes it gets into the mode of scrolling L to R or Top to 
> Bottom
> 4. At that point it will NOT scroll the records leaving the only way to do 
> so is via the
>     L/R slide bar in the LHS status window - which is cumbersome
> 5. The only to give record scrolling back to the mouse wheel is to exit and 
> re-enter
>     the data base
> 6. How can I lock the record scrolling to the mouse wheel and layout panning 
> be
>     left only to the side and bottom scroll bars regardless of the screen 
> magnification
> 
> Best Regards Ron H. 

As far as I know, you can't.

Ron H. said:
> 6. How can I lock the record scrolling to the mouse wheel and layout panning 
> be left only to the side and bottom scroll bars regardless of the screen 
> magnification

Scrolling behaviour is controlled by the Operating System, or the 
software that comes with you device. Filemaker has no control over this 
behaviour.

Typically, scrolling is effective on wherever the O.S. is focused at the 
moment. As long as you have a layout that is larger than the available 
screen, you will have no control over what the scroll wheel does.

Kent

On 4/9/2005, KV wrote:

> Scrolling behaviour is controlled by the Operating System, or the
> software that comes with you device. Filemaker has no control over
> this behaviour.

I beg to differ. 

The typical behavior is to scroll up or down a window according to the
location of the pointer, this is still somthing that the developer has
to program into the application. If the application is not told what to
do, it won't do it.

That alone tells me there is absolutely nothing stopping FM from
providing a choice as to whether the scrolling control moves up and
down the screen or back and forth through the records. It is just a
matter of telling the application what to do upon receiving the
scrolling instruction.

Matt

In article <UpV5e.3396$Fm5.731@trndny09>, nothanks@verizon.net says...
> 
> 
> On 4/9/2005, KV wrote:
> 
> > Scrolling behaviour is controlled by the Operating System, or the
> > software that comes with you device. Filemaker has no control over
> > this behaviour.
> 
> I beg to differ. 
> 
> The typical behavior is to scroll up or down a window according to the
> location of the pointer, this is still somthing that the developer has
> to program into the application. If the application is not told what to
> do, it won't do it.
> 
> That alone tells me there is absolutely nothing stopping FM from
> providing a choice as to whether the scrolling control moves up and
> down the screen or back and forth through the records. It is just a
> matter of telling the application what to do upon receiving the
> scrolling instruction.

Yes. There is nothing stopping FM from providing a choice.

However, they didn't.

Matt Wills said:
> 
> On 4/9/2005, KV wrote:

>>Scrolling behaviour is controlled by the Operating System, or the
>>software that comes with you device. Filemaker has no control over
>>this behaviour.

> I beg to differ. 
> 
> The typical behavior is to scroll up or down a window according to the
> location of the pointer, this is still somthing that the developer has
> to program into the application. If the application is not told what to
> do, it won't do it.
> 
> That alone tells me there is absolutely nothing stopping FM from
> providing a choice as to whether the scrolling control moves up and
> down the screen or back and forth through the records. It is just a
> matter of telling the application what to do upon receiving the
> scrolling instruction.
> 
> Matt

My apologies. I communicated poorly. The O.S. or software decides what 
code the scroll wheel sends. In most cases, it sends a predefined code, 
or set of codes, that tell the application that the user requested a 
scroll. The application could chose to let you do what you want with 
those clicks, or they could simply carry out their default action. 
Because Filemaker has not provided access to those codes, all you can do 
is cross your fingers that the default action will be what you want it 
to be. I am not aware of anything that will let you take control of 
these actions unless the application has specifically granted that control.

Kent

Thankyou all for your efforts,
Having said that, what is the best method that I can program in to "scroll" 
through the records - seeing the records as I pass through them (similar to 
mouse wheel)
Clicking the slide bar in the LHS status window is only 1 record per click 
which means it is slow because you can't "hold the scroll direction down". 
Any ideas on this?
Best Regards Ron H.


"KV" <noone@invalid.invalid> wrote in message 
news:dBW5e.937533$Xk.508473@pd7tw3no...
> Matt Wills said:
>>
>> On 4/9/2005, KV wrote:
>
>>>Scrolling behaviour is controlled by the Operating System, or the
>>>software that comes with you device. Filemaker has no control over
>>>this behaviour.
>
>> I beg to differ. The typical behavior is to scroll up or down a window 
>> according to the
>> location of the pointer, this is still somthing that the developer has
>> to program into the application. If the application is not told what to
>> do, it won't do it.
>>
>> That alone tells me there is absolutely nothing stopping FM from
>> providing a choice as to whether the scrolling control moves up and
>> down the screen or back and forth through the records. It is just a
>> matter of telling the application what to do upon receiving the
>> scrolling instruction.
>>
>> Matt
>
> My apologies. I communicated poorly. The O.S. or software decides what 
> code the scroll wheel sends. In most cases, it sends a predefined code, or 
> set of codes, that tell the application that the user requested a scroll. 
> The application could chose to let you do what you want with those clicks, 
> or they could simply carry out their default action. Because Filemaker has 
> not provided access to those codes, all you can do is cross your fingers 
> that the default action will be what you want it to be. I am not aware of 
> anything that will let you take control of these actions unless the 
> application has specifically granted that control.
>
> Kent
> 

> what is the best method that I can program in to "scroll"
> through the records - seeing the records as I pass through them (similar to
> mouse wheel)
> Clicking the slide bar in the LHS status window is only 1 record per click
> which means it is slow because you can't "hold the scroll direction down".

I never had a need for that, but perhaps you could create two buttons on
your layout, button 1 would run the following script

Loop
Go to record/request/page (next)
Pause/resume script (1 second)
End loop

The second button would do the following to stop the script when you get to
the record you are scrolling for.

Halt script

Not sure if this does what you set out to do.

You could try experimenting with the pause time (half second, 3/4 second) to
try and get it to a pace where you can absorb the data you are 'scrolling'
through.

On the other hand, you could just create a script that uses the go to
record/request/page (next) multiple times so you can forward through the
records, say, 5 at a time with each click.



Geoff

Are you on Mac (9 or X?) or Windows?  I can't speak for Mac, but on 
WIndows, scrolling in both list view and form view will scroll through 
records.  Are you saying that yours is doing something different but you 
want it to just scroll through records?

(I've always thought and wished that it should scroll through records in 
list or table view, but that it should just scroll up and down on the 
current layout while in form view.)

Ron H. wrote:
> Thankyou all for your efforts,
> Having said that, what is the best method that I can program in to "scroll" 
> through the records - seeing the records as I pass through them (similar to 
> mouse wheel)
> Clicking the slide bar in the LHS status window is only 1 record per click 
> which means it is slow because you can't "hold the scroll direction down". 
> Any ideas on this?
> Best Regards Ron H.
> 
> 
> "KV" <noone@invalid.invalid> wrote in message 
> news:dBW5e.937533$Xk.508473@pd7tw3no...
> 
>>Matt Wills said:
>>
>>>On 4/9/2005, KV wrote:
>>
>>>>Scrolling behaviour is controlled by the Operating System, or the
>>>>software that comes with you device. Filemaker has no control over
>>>>this behaviour.
>>
>>>I beg to differ. The typical behavior is to scroll up or down a window 
>>>according to the
>>>location of the pointer, this is still somthing that the developer has
>>>to program into the application. If the application is not told what to
>>>do, it won't do it.
>>>
>>>That alone tells me there is absolutely nothing stopping FM from
>>>providing a choice as to whether the scrolling control moves up and
>>>down the screen or back and forth through the records. It is just a
>>>matter of telling the application what to do upon receiving the
>>>scrolling instruction.
>>>
>>>Matt
>>
>>My apologies. I communicated poorly. The O.S. or software decides what 
>>code the scroll wheel sends. In most cases, it sends a predefined code, or 
>>set of codes, that tell the application that the user requested a scroll. 
>>The application could chose to let you do what you want with those clicks, 
>>or they could simply carry out their default action. Because Filemaker has 
>>not provided access to those codes, all you can do is cross your fingers 
>>that the default action will be what you want it to be. I am not aware of 
>>anything that will let you take control of these actions unless the 
>>application has specifically granted that control.
>>
>>Kent
>>
> 
> 
> 

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg              (818) 883-2846
FM Pro Solutions       Los Angeles, California

FileMaker 7 Certified Developer
Associate Member, FileMaker Solutions Alliance

Hi Howard,
1. Previous posts have validated that there is no way to keep the "focus" of 
the Mouse Wheel  on scrolling through Records once that "focus" has moved to 
L->R or T->B scrolling on large layouts or where the layout has been Zoomed 
in on
2. The only way to return Mouse Wheel "focus" back to Record Scrolling is to 
either
    a. exit and re-enter database
    b. Zoom out to remove scroll bars and then "re-align" the Mouse Wheel 
"focus" by entering another FM object like Scripts or Drop Down Lists that 
use the Mouse Wheel, exercise the Mouse Wheel and return to the layout and 
presto Record scrolling can again take place via the Mouse Wheel
3. This is not particularly user friendly because users will Zoom in and out 
and will not understand the technique of getting the Mouse Wheel "focus" 
back
4. The advantage of MW Record scrolling is that
    a. It is quick
    b. It allows viewing of the records as you pass through  - one by one at 
various speeds
5. I can set up Record FWD and BWD buttons on the layout - but they have 2 
problems
    a. They are relatively slow compared to the FWD and BWD button in the 
Status Area
    b. In either case to scroll through 100 records you have to do 100 
clicks of mouse button
6. I would like to simulate the MW by having FWD and BWD buttons on the 
layout such that :-
    a. A single click progresses to the next record - either FWD or BWD
    b. "Holding the button down" advances the records continuously at some 
fixed speed (perhaps 1 record / sec) - but lets you glimpse the records as 
they pass by
7. Is there a programmatic way to achieve this in a Windows XP environment
8. I understand this is a "replacement" for the ultimate MW Record scrolling 
which will get lost when top and side scroll bars appear

Regards Ron H.

"Howard Schlossberg" <howard@antispahm.fmprosolutions.com> wrote in message 
news:115h2ob46d41702@corp.supernews.com...
> Are you on Mac (9 or X?) or Windows?  I can't speak for Mac, but on 
> WIndows, scrolling in both list view and form view will scroll through 
> records.  Are you saying that yours is doing something different but you 
> want it to just scroll through records?
>
> (I've always thought and wished that it should scroll through records in 
> list or table view, but that it should just scroll up and down on the 
> current layout while in form view.)
>
> Ron H. wrote:
>> Thankyou all for your efforts,
>> Having said that, what is the best method that I can program in to 
>> "scroll" through the records - seeing the records as I pass through them 
>> (similar to mouse wheel)
>> Clicking the slide bar in the LHS status window is only 1 record per 
>> click which means it is slow because you can't "hold the scroll direction 
>> down". Any ideas on this?
>> Best Regards Ron H.
>>
>>
>> "KV" <noone@invalid.invalid> wrote in message 
>> news:dBW5e.937533$Xk.508473@pd7tw3no...
>>
>>>Matt Wills said:
>>>
>>>>On 4/9/2005, KV wrote:
>>>
>>>>>Scrolling behaviour is controlled by the Operating System, or the
>>>>>software that comes with you device. Filemaker has no control over
>>>>>this behaviour.
>>>
>>>>I beg to differ. The typical behavior is to scroll up or down a window 
>>>>according to the
>>>>location of the pointer, this is still somthing that the developer has
>>>>to program into the application. If the application is not told what to
>>>>do, it won't do it.
>>>>
>>>>That alone tells me there is absolutely nothing stopping FM from
>>>>providing a choice as to whether the scrolling control moves up and
>>>>down the screen or back and forth through the records. It is just a
>>>>matter of telling the application what to do upon receiving the
>>>>scrolling instruction.
>>>>
>>>>Matt
>>>
>>>My apologies. I communicated poorly. The O.S. or software decides what 
>>>code the scroll wheel sends. In most cases, it sends a predefined code, 
>>>or set of codes, that tell the application that the user requested a 
>>>scroll. The application could chose to let you do what you want with 
>>>those clicks, or they could simply carry out their default action. 
>>>Because Filemaker has not provided access to those codes, all you can do 
>>>is cross your fingers that the default action will be what you want it to 
>>>be. I am not aware of anything that will let you take control of these 
>>>actions unless the application has specifically granted that control.
>>>
>>>Kent
>>>
>>
>>
>>
>
> -- 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Howard Schlossberg              (818) 883-2846
> FM Pro Solutions       Los Angeles, California
>
> FileMaker 7 Certified Developer
> Associate Member, FileMaker Solutions Alliance 

I haven't actually tried this, but could you button-script a loop to 
scroll through each record at a sedate pace and exit the loop if a key 
or mouse button is pressed?

Another option might be a button that scrolls forward or back 5 or 10 
records, rather than 1?

Kent


Ron H. said the following on 4/09/05 20:57:
> Hi Howard,
> 1. Previous posts have validated that there is no way to keep the "focus" of 
> the Mouse Wheel  on scrolling through Records once that "focus" has moved to 
> L->R or T->B scrolling on large layouts or where the layout has been Zoomed 
> in on
> 2. The only way to return Mouse Wheel "focus" back to Record Scrolling is to 
> either
>     a. exit and re-enter database
>     b. Zoom out to remove scroll bars and then "re-align" the Mouse Wheel 
> "focus" by entering another FM object like Scripts or Drop Down Lists that 
> use the Mouse Wheel, exercise the Mouse Wheel and return to the layout and 
> presto Record scrolling can again take place via the Mouse Wheel
> 3. This is not particularly user friendly because users will Zoom in and out 
> and will not understand the technique of getting the Mouse Wheel "focus" 
> back
> 4. The advantage of MW Record scrolling is that
>     a. It is quick
>     b. It allows viewing of the records as you pass through  - one by one at 
> various speeds
> 5. I can set up Record FWD and BWD buttons on the layout - but they have 2 
> problems
>     a. They are relatively slow compared to the FWD and BWD button in the 
> Status Area
>     b. In either case to scroll through 100 records you have to do 100 
> clicks of mouse button
> 6. I would like to simulate the MW by having FWD and BWD buttons on the 
> layout such that :-
>     a. A single click progresses to the next record - either FWD or BWD
>     b. "Holding the button down" advances the records continuously at some 
> fixed speed (perhaps 1 record / sec) - but lets you glimpse the records as 
> they pass by
> 7. Is there a programmatic way to achieve this in a Windows XP environment
> 8. I understand this is a "replacement" for the ultimate MW Record scrolling 
> which will get lost when top and side scroll bars appear
> 
> Regards Ron H.
> 
> "Howard Schlossberg" <howard@antispahm.fmprosolutions.com> wrote in message 
> news:115h2ob46d41702@corp.supernews.com...
> 
>>Are you on Mac (9 or X?) or Windows?  I can't speak for Mac, but on 
>>WIndows, scrolling in both list view and form view will scroll through 
>>records.  Are you saying that yours is doing something different but you 
>>want it to just scroll through records?
>>
>>(I've always thought and wished that it should scroll through records in 
>>list or table view, but that it should just scroll up and down on the 
>>current layout while in form view.)
>>
>>Ron H. wrote:
>>
>>>Thankyou all for your efforts,
>>>Having said that, what is the best method that I can program in to 
>>>"scroll" through the records - seeing the records as I pass through them 
>>>(similar to mouse wheel)
>>>Clicking the slide bar in the LHS status window is only 1 record per 
>>>click which means it is slow because you can't "hold the scroll direction 
>>>down". Any ideas on this?
>>>Best Regards Ron H.
>>>
>>>
>>>"KV" <noone@invalid.invalid> wrote in message 
>>>news:dBW5e.937533$Xk.508473@pd7tw3no...
>>>
>>>
>>>>Matt Wills said:
>>>>
>>>>
>>>>>On 4/9/2005, KV wrote:
>>>>
>>>>>>Scrolling behaviour is controlled by the Operating System, or the
>>>>>>software that comes with you device. Filemaker has no control over
>>>>>>this behaviour.
>>>>
>>>>>I beg to differ. The typical behavior is to scroll up or down a window 
>>>>>according to the
>>>>>location of the pointer, this is still somthing that the developer has
>>>>>to program into the application. If the application is not told what to
>>>>>do, it won't do it.
>>>>>
>>>>>That alone tells me there is absolutely nothing stopping FM from
>>>>>providing a choice as to whether the scrolling control moves up and
>>>>>down the screen or back and forth through the records. It is just a
>>>>>matter of telling the application what to do upon receiving the
>>>>>scrolling instruction.
>>>>>
>>>>>Matt
>>>>
>>>>My apologies. I communicated poorly. The O.S. or software decides what 
>>>>code the scroll wheel sends. In most cases, it sends a predefined code, 
>>>>or set of codes, that tell the application that the user requested a 
>>>>scroll. The application could chose to let you do what you want with 
>>>>those clicks, or they could simply carry out their default action. 
>>>>Because Filemaker has not provided access to those codes, all you can do 
>>>>is cross your fingers that the default action will be what you want it to 
>>>>be. I am not aware of anything that will let you take control of these 
>>>>actions unless the application has specifically granted that control.
>>>>
>>>>Kent
>>>>
>>>
>>>
>>>
>>-- 
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>Howard Schlossberg              (818) 883-2846
>>FM Pro Solutions       Los Angeles, California
>>
>>FileMaker 7 Certified Developer
>>Associate Member, FileMaker Solutions Alliance 
> 
> 
> 

On Sat, 09 Apr 2005 16:14:18 GMT, KV wrote:
>  Scrolling behaviour is controlled by the Operating System, or the 
>  software that comes with you device. Filemaker has no control over this 
>  behaviour.

Filemaker has lots of control here :-(

Example: MacOS does support scrolling. The typical Mac comes with a
single button mouse, but most USB mice with scroll wheel will work from
the box. New PowerBooks support trackpad scrolling.

However, FileMaker *DISABLED* scrolling.
(In fact, it's supported on Win. It's disabled on Mac only)

- Martin