1 person found this helpful
Edit your setBusyCursor function to this:
private function setBusyCursor():void
In the documentation for CursorManager, it states:
"In AIR, each mx.core.Window instance uses its own instance of the CursorManager class. Instead of directly referencing the static methods and properties of the CursorManager class, use the
Window.cursorManagerproperty to reference the CursorManager instance for the Window instance."
I just discovered this today.
Ok, but I've noticed MXML components like RemoteObject and HTTPService that also use "showBusyCursor=true" also result in the cursor disappearing. How can I apply the same method to the MXML components?
To add to myIP's post, I had to use parentApplication.cursorManager.setBusyCursor() if executing this code within a component. "this" only works if the code is executed inside the Window() instance.
So how does this affect FLEX?
I am confused, is this only happening in an AIR app, or a FLEX app?
I can use [CursorManager.setBusyCursor();]
I thought I was using 4.1, but I think I am only using 4.0...is this a new FLEX bug or something? Or just an bug in AIR?
I doubt it will be affecting non-AIR apps because this issue is occurring inside a new Window(), which is an AIR feature.