flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Harui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-16796) RemoteObject showBusyCursor displayed in wrong window
Date Sun, 07 Sep 2014 05:02:29 GMT

    [ https://issues.apache.org/jira/browse/FLEX-16796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124770#comment-14124770

Alex Harui commented on FLEX-16796:

This is one of those times I regret that Flex ever had the showBusyCursor option on RemoteObject.
Of course, we put it there before there was AIR and multi-window apps.   Looks like someone
suggested a patch but never submitted it.  But I think that solution would only work if you
specify your Windows in MXML.  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.  I think we'd need
to add a way to pass RemoteObject a displayObject or cursorManager to use.  BTW, in the more
general case, should EVERY AIR window show the busy cursor while waiting for an RemoteObject
operation to return?

Also, is the workaround to call CursorManager.removeBusyCursor and then cursorManager.showBusyCursor
in the Window? (Note the big "C" on remove, and small "c" on show).

> 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

View raw message