This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 191672 - Cursor does not always change when mouse is over frameborder
Summary: Cursor does not always change when mouse is over frameborder
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-05 13:21 UTC by mortennobel
Modified: 2010-11-14 21:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mortennobel 2010-11-05 13:21:19 UTC 
The mouse cursor does not always into 'drag arrows' (horizontal or vertical) when the mouse is positioned over the frame border (such as between the editor panel and the output panel or between the editor panel and the project panel).

The bug is not consistent. Sometimes it works correctly on all borders. Other times it does not work on any border. I haven't found a pattern of when the problem appears, but sometimes it appears when I return to Netbeans after running the OpenGL/GLUT program I'm working on.



Product Version = NetBeans IDE Dev (Build 201011050000)
Operating System = Mac OS X version 10.6.4 running on x86_64
Java; VM; Vendor = 1.6.0_22
Runtime = Java HotSpot(TM) 64-Bit Server VM 17.1-b03-307
Comment 1 Stanislav Aubrecht 2010-11-11 09:16:48 UTC 
it happens when most of netbeans heap memory is swapped out to disk. when you return to netbeans after long period of inactivity it needs some time to load some stuff from disk so the cursor doesn't react for a moment.
Comment 2 mortennobel 2010-11-14 21:29:54 UTC 
I don't think it is related to swapping heap memory to/from disk. The cursor problem does seem to fix itself unless I do some actions (such as modifying the viewports) - other actions, such as clicking on the editor, does not seem to help.