You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Peter Ginneberge (JIRA)" <ji...@apache.org> on 2014/09/07 05:28:28 UTC

[jira] [Commented] (FLEX-16796) RemoteObject showBusyCursor displayed in wrong window

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

Peter Ginneberge commented on FLEX-16796:
-----------------------------------------

Damn, 5 years later this bug hasn't been fixed.. ouch.

Using Flex 4.9.1 with AIR 3.7 on Windows and just encountered this bug.

The main application window functions as a splash screen. The actual application is a Window component created by the splash screen after which the splash screen is hidden (visible = false). Any service (HTTP, Remote, etc..) with showBusyCursor=true will hide the system cursor and the busy cursor never shows. I'm guessing it is displayed in the hidden main application window.

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