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 Mon, 08 Sep 2014 16:25:28 GMT

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

Alex Harui commented on FLEX-16796:
-----------------------------------

Well, there is no single instance of CursorManager in a multi-Window AIR app.  Each Window
gets its own instance of CursorMangerImpl to manage the "stack" of cursors.  The old APIs
still exist and default to the initial Application window and probably need to keep doing
that for backward-compatibility reasons.

That's why calling the Window's cursorManager.setBusyCursor() should work.  The lower-case
"c" cursorManager in the code for a Window or Application references the CursorManagerImpl
for that window.  The upper-case "C" CursorManager is using the old APIs.

But still, IMO, the fundamental issue is that RemoteObject is not associated with a Window,
not that the setBusyCursor APi needs association with a Window.  In a more complex multi-Window
app, I think it would be too hard to use a displayBusyCursorOn API.  So, I think one answer
is to be able to pass RemoteObject either a UIComponent or the instance of a CursorManagerImpl
it should use.  

That said, the true answer may be to just document that RemoteObject.showBusyCursor is a convenience
for the main app window and other scenarios require use of cursorManager directly.  Someone
who does want to display busy cursors in more than two windows that are waiting for data from
a shared RemoteObject will find that passing a single Window or cursorManager to RemoteObject
will be too restrictive.


> 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)

Mime
View raw message