[
https://issues.apache.org/jira/browse/FLEX-16796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124811#comment-14124811
]
Peter Ginneberge commented on FLEX-16796:
-----------------------------------------
{quote}
Essentially, the problem is that in many cases, RemoteObject/HTTPService, etc
doesn't know which Window you want to use to show the busy cursor
{quote}
Well to be honest, the way it is now (always and only display in
WindowedApplication) makes the least sense, especially for AIR.
{quote}should EVERY AIR window show the busy cursor{quote}
IMO, no. Only the current focused/active window or one defined by the user
(dev).
{quote}Also, is the workaround to call CursorManager.removeBusyCursor and then
cursorManager.showBusyCursor in the Window?{quote}
No idea, haven't tried. But in my case (and in any multi window application)
that wouldn't help much, as the services are not part of the Window (MVC). The
Window dispatches an Event, Controller executes Command, Command invokes
Service. So when the Window dispatches an Event and then calls
removeBusyCursor/showBusyCursor, there may actually not be any cursor yet. And
there's other complicated scenarios where you may actually end up being stuck
with a busy cursor for instance.
> 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)
