Hi Alex
Thanks for replying, though I must confess I don't really understand
your answer. Please bear with me.
Are you saying that the UMap component is doing something it oughtn't?
Or is your reply based on my (perhaps) poorly phrased question?
In other words, are you saying that the error message I've presented
here means that UMap is doing something it shouldn't, or just that if
it *were* doing that you'd expect to see that message?
The app we're working on is reasonably complex, but I'm not doing
anything overly clever in it - at least, I've never done anything to
cause an error like this previously.
Guy
On 28/08/2008, at 2:06 PM, Alex Harui wrote:
There is an assumption that the Flex Application is at index 1 in
the SystemManager. A mouseShield goes at 0. We don’t officially
support slipping anything behind the Application. You could try
adjusting the mx_internal applicationIndex to be the right number.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED]
On Behalf Of Guy Morton
Sent: Wednesday, August 27, 2008 4:27 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] UMap problem
Has anyone else here got experience with using UMap and know the
answer to this problem?
http://www.afcomponents.com/components/umap_as3/
I have an existing mapping app that has other layers over the map. If
I put a UMap map under these layers and click on pretty much anything
that sits over the map I get this error:
ArgumentError: Error #2025: The supplied DisplayObject must be a child
of the caller.
at flash.display::DisplayObjectContainer/getChildIndex()
at mx.managers::SystemManager/getChildIndex()[C:\dev\flex_201_gmc\sdk
\frameworks\mx\managers\SystemManager.as:1270]
at mx.managers::SystemManager/mouseDownHandler()[C:\dev\flex_201_gmc
\sdk\frameworks\mx\managers\SystemManager.as:2478]
Any clues? Am I doing something wrong? Does UMap just not like having
other objects sitting over the top of it? I hope that's not the case
as it would mean we can't use it.
Guy
