J. Landman Gay
jacque at hyperactivesw.com
Tue Apr 20 21:41:39 CDT 2010
Graham & Heather Harrison wrote:
> Hi Jacqueline,
>> If you need to double-click then I think there must be a script
>> interfering. Rev uses standard click behaviors by default.
> I am forced to use double-click in the channel on every scrollable
> rev screen, including Application Browser and Script Editing.
Definitely non-standard, I've never seen this in any version of Rev. Do
you have a custom mouse driver? System settings? Extensions? Something
about your setup is different.
>> They should use the system setting for arrows though, which in my
>> case is to show double arrows at the bottom. Not sure what you mean
>> by two arrows at either end.
> By two arrows I mean double arrows. This is a system setting which
> cannot be reached through normal preferences. Can be set by
> TinkerTool, MacPilot, etc. As I said, rev recognises this correctly.
You can set this in System Preferences/Appearance. Which version os OS X
are you using? If it's an older version (one that didn't have that
preference option,) and you've used Tinkertool on it, I wonder if that
makes a difference. In fact, if it's too old, I'm not sure Rev will
support it fully.
>> You may have to script the "go to here" part, since scrollbars by
>> default use the pageinc property to determine how far to scroll.
> This is where I need help, as a rev newbie. WhatI want to do is
> somehow bypass/overwrite the system values, not redefine scrolling
> from the top down. So, for example, how do I find the scrolling
> system values?
Well, each field or group property inspector has the settings, and if
you're using an independent scrollbar (unattached to a field or group)
then the scrolbar object itself has those settings in its property
inspector. You'd need to change the settings on every scrolling object,
but if you're seeing the behavior in the IDE, the settings aren't the
problem. The IDE is already written to act as you'd expect. In fact, I
can't think of any property settings that would allow you to restore
"normalcy", because the default behavior is "normal", and it would take
some fancy scripting to override it so that it responded only to
I'm pretty sure if your experience was common, the bug database would be
full of reports. So we need to figure out what's different with your OS.
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
More information about the use-livecode