a minor cosmetic annoyance

[Peter Brigham]

On Wed, 16 Apr 2008 10:36:35 -0700, Richard Gaskin  
<ambassador at fourthworld.com> wrote:

> Peter Brigham wrote:
>> I don't know if anyone else is annoyed by this behavior.... When you
>> have an unlocked scrolling field and you move the cursor into it, it
>> changes to an ibeam. The problem for me is that it's an ibeam even if
>> you move the cursor over the scrollbar.
>
> I think there may be something else at play there.
>
> I just did this test:
>
> 1. Create a new stack
> 2. Add a field control
> 3. Switch to browse tool
> 4. Move mouse between text area and scrollbar
>
> - the cursor updated as expected.
>
> Perhaps the lockCursor is set for some reason?


Hmm. I'll check that out. I have long been bothered by the persistent  
ibeam problem, and I tested it again with a virgin stack and one  
scrolling field before writing the above email, and it behaved as I  
described -- but I had not closed Rev first and had been working in  
the stack system I spend most of my time with (practice management).  
I thought I had cleaned out all the "lock cursor" commands from that  
stack system, but it looks as if there is something in my system that  
locks the cursor. Now quite sure how, exactly, because I have  
mouseleave handlers that unlock the cursor in a number of my  
controls. But when I restarted Rev just now and once more made a  
virgin stack and scrolling field, it behaves properly. I've got some  
more detective work to do. Meanwhile, as Emily Latella used to say on  
the old Saturday Night Live.... "never mind."

Peter M. Brigham
pmbrig at gmail.com