Mailing-List: contact users-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@flex.apache.org
Date: Sun, 9 Aug 2015 21:51:19 +0000 (UTC)
From: Dave Glasser <dglasser@pobox.com>
Reply-To: Dave Glasser <dglasser@pobox.com>
To: "users@flex.apache.org" <users@flex.apache.org>
Message-ID: <1958220792.1574061.1439157079619.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: 
 <CANF6s8Ah-dMx_+2Pg1sbTX4zxZV-7Zo5JB1ajLgr8HsZrGVs+w@mail.gmail.com>
References: 
 <CANF6s8Ah-dMx_+2Pg1sbTX4zxZV-7Zo5JB1ajLgr8HsZrGVs+w@mail.gmail.com>
Subject: Re: Using Flex Drag Manager in AIR WindowedApplication
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1574060_670132522.1439157079615"

------=_Part_1574060_670132522.1439157079615
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks Rudolf, but that didn't work. Same exact behavior. And what's intere=
sting is that the mouse cursor appears over the main application window whe=
n I'm dragging as well. It disappears in the window in which I'm dragging, =
but the app is obviously tracking the mouse location in the window in which=
 I'm dragging, because when I (blindly) drag over something that won't acce=
pt the drop, the mouse cursor gets the additional red circle-X, and when I =
(blindly) drop over something that can accept it, the drop code works as ex=
pected.

      From: Rudolf Schnetler <rudolf@stripedog.com>
 To: users@flex.apache.org; Dave Glasser <dglasser@pobox.com>=20
 Sent: Sunday, August 9, 2015 5:11 PM
 Subject: Re: Using Flex Drag Manager in AIR WindowedApplication
  =20
Try setting setting 'mouseChildren =3D false' in the application window
before dragging and to true when drag finished.


On Mon, Aug 10, 2015 at 5:22 AM, Dave Glasser <dglasser@pobox.com> wrote:

> I'm using Flex 4.13.0. I'm porting a browser-based Flex app to the AIR
> platform, as a multi-window application. The main window will be used to
> configure server connections, and the child windows will be login session=
s
> to individual servers -- essentially what you would see in the
> browser-based application.
>
> The code already uses a lot of drag/drop that works well in the browser.
> It didn't work so well in the AIR app, so I switched the AIR app to not u=
se
> the native drag manager, but rather the same DragManagerImpl class as the
> browser app, by doing this in the main MXML file:
>
> <s:WindowedApplication
>=C2=A0 =C2=A0 xmlns:fx=3D"http://ns.adobe.com/mxml/2009"
>=C2=A0 =C2=A0 xmlns:mx=3D"library://ns.adobe.com/flex/mx"
>=C2=A0 =C2=A0 xmlns:s=3D"library://ns.adobe.com/flex/spark"
>=C2=A0 =C2=A0 useNativeDragManager=3D"false">
>
>
> Anyway, a lot of the problems I had with the native drag manager have gon=
e
> away. But there's one huge new problem. The DragProxy is parented by the
> main application window, so while I'm dragging something within a child
> window, I see my dragImage (which is parented by the DragProxy) moving
> around within the main application window.
>
> In DragManagerImpl.doDrag(), I see this:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 // The drag proxy is a UIComponent with a sing=
le child -
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 // an instance of the dragImage.
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 dragProxy =3D new DragProxy(dragInitiator, dra=
gSource);
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 var e:Event;
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (hasEventListener("popUpChildren"))
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 e =3D new DragEvent("popUpChildr=
en", false, true, dragProxy);
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (!e || dispatchEvent(e))
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 sm.popUpChildren.addChild(dragPr=
oxy);
>
>
> And here, sm seems to always be the ISystemManager of the main applicatio=
n
> window. I don't see any other code where the DragProxy is added to the
> display list.
>
>
> Does anyone have any ideas how I can get this to work?
>
>
>
>


------=_Part_1574060_670132522.1439157079615--