[FLEX-25500] setBusyCursor() causes cursor to completely disappear when set inside a new Window() instance

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Adobe Flex SDK 4.1 (Release)
• Component/s: Cursor Manager
• Environment: Affected OS(s): All OS Platforms; Affected OS(s): All OS Platforms; Language Found: English
• Assignee: Unassigned
• Reporter: Adobe JIRA
• Created: 04/Oct/10 04:15
• Updated: 05/Oct/10 00:35

Description

See attached FXP file. Using Flex 4.1 or 4.5 this issue can easily be replicated by calling CursorManager.setBusyCursor() inside a new Window() instance. The result is the cursor completely disappears and doesn't return either until removeBusyCursor() is called or the app is restarted.