🚀 go-pugleaf

"Michael D. Spence" <spence@panix.com> wrote in message 
news:423b3a96$1@newsgroups.borland.com...
> "Lori M Olson [TeamB]" <javadragon@techie.com> wrote in message 
> news:423b0e14$1@newsgroups.borland.com...
>> Michael D. Spence wrote:
>>
>>> I have a JPanel that is contained in a JInternalFrame.  In response to a 
>>> mouse click, the JPanel changes the cursor to a custom cursor while a 
>>> database operation is going on, then changes it back to the previous 
>>> cursor.
>>>
>>> This works fine on my development system, but when the app. is 
>>> distributed to the user and they click on the JPanel, the cursor change 
>>> only shows as long as the user keeps the mouse button pressed.  As soon 
>>> as they release the mouse, the cursor changes back.
>>>
>>> Also on my development system (and as one would expect), the custom 
>>> cursor is replaced by the system default when it's moved outside of the 
>>> applicaton window.  But when the cursor is moved back onto my app 
>>> window, it changes to a horizontal sizing cursor (double-ended arrow), 
>>> which eventually changes back to the original default cursor on 
>>> schedule, when the database operation completes.
>>>
>>> I have no idea what could be going on here.  Help!
>>>
>>>
>>> ________________________
>>> Michael D. Spence
>>> Mockingbird Data Systems, Inc.
>>
>> Perhaps if you posted some of the mouse cursor setting code...
>>
>
> Sure.  Here you are:
>
>    Cursor c = this.getCursor();
>    this.setCursor(dataUtils.getSqlCursor());
>    try {
>      ... Database work occurs here ...
>    } finally {
>      this.setCursor(c);
>    }
>
>
> dataUtils returns a Cursor object, which works fine on my development 
> system but not on the user's system.
>
> But just in case, instead of using that, I'm going to try this to see what 
> happens:
>
>    this.setCursor(Cursor.getPredefinedCursor(Cursor.WAIT_CURSOR));
>


Ok, using a regular wait cursor solves the second problem (where the cursor 
is totally lost when
the mouse moves outside the app's main window), but I wonder if it'll solve 
the first, where
the custom cursor is only displayed while the mouse button is held down.

I'm guessing this has something to do with the custom cursor not being 
available to whatever deals
with the mouse leaving and re-entering the app window.