02-28-2008 6:18 PM
I cant seem to get a simple use case to work:
I have an AIR app that has two <mx:Window> built as separate MXML components, one is called DragSourceWindow the other DragTargetWindow. Inside the DragSourceWindow is a canvas that can be dragged out of the window and dropped into the DragTargetWindow.
Code:
Main AIR App: http://pastie.caboo.se/private/wxcsvvxglm7aabf3xqta
DragTargetWindow: http://pastie.caboo.se/private/ysgv3kpr6suiakutnvt4g
DragSourceWindow: http://pastie.caboo.se/private/yybaslwsfz12znygyjvva
SVN Repo: http://zclguialvgrid.googlecode.com/svn/trunk/examples/DragManagerIssue/
Inside each <mx:Window> are some trace messages to see what is going on:
1. When a DragManager.isDragging is true
2. When you drag into a drop target
3. When you drop an item into a drop target
However, once you drop the canvas into a window and mouseover it again the DragManager still thinks a drag is active.
I am using the release versions of FB and AIR.
What am I doing wrong?
02-28-2008 8:40 PM
Nevermind, you can't use DragManager at all in AIR it seems if you leave a window. You have to directly use the NativeDragManager.
Strange because it seems like the DragManager singleton manages that for you -- but it doesn't.