[
https://issues.apache.org/jira/browse/FLEX-16796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125189#comment-14125189
]
Alex Harui commented on FLEX-16796:
-----------------------------------
OK, so do you think the right answer is to add a property to RemoteObject (etc)
to specify either the cursorManager or some UIComponent in the Window?
FWIW, a better workaround may be to not use RemobeObject.showBusyCursor and
instead in the Window, call cursorManager.setBusyCursor after the Event is
dispatched, and call cursorManager.removeBusyCursor when the results arrive.
> RemoteObject showBusyCursor displayed in wrong window
> -----------------------------------------------------
>
> Key: FLEX-16796
> URL: https://issues.apache.org/jira/browse/FLEX-16796
> Project: Apache Flex
> Issue Type: Bug
> Components: RPC: RemoteObject
> Affects Versions: Adobe Flex SDK 3.2 (Release), Apache Flex 4.9.0
> Environment: Affected OS(s): Mac
> Affected OS(s): Mac OS 10.5
> Browser: Other (specify version)
> Language Found: English
> Reporter: Adobe JIRA
>
> Steps to reproduce:
> 1. Create a AIR WindowedApplication (AIR 1.5, SDK/Builder 3.2)
> 2. create a custom component based on the mx:Window and open that window when
> the WindowedApplication is started
> 3. make RemoteObject call to a CFC (in my case) and set the showBusyCursor to
> true
>
> Actual Results:
> The busy cursor is displayed in the WindowApplication (the main app window)
>
> Expected Results:
> Busy cursor should be displayed in the window the RemoteObject is used
> instead of the main app window
>
> Workaround (if any):
> None so far
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
