Hello!
I have two similar situation:
1) I have a canvas and child controls that is situated by center (i.e.). Canvas and child are allowed drop. When I drag an item I want to get following scenario: First DropQuery event handled by child with, then if the query result is false (or null) - it handled by canvas itself.
But now I have following problems:
a) when I moving over child element and child element set null (or false) to query result I got incorrect RelativeDragPoint for canvas (Their don't change from after child).
b) In the some points (suggest nea border) - I got unnecessary drop impossibel info
c) If child return true for query - why drop quary event handleb on canvas?
Stack trace actions:
With child:
Drop query child status: DropDestinationQuery, x: 45, y: 21
Drop query canvas status: DropDestinationQuery, x: 45, y: 21
Drag query drag element status: DropSourceQuery, x: 45, y: 21
Drop info canvas status: DropPossible, x: 45, y: 21
Drag info drop element status: DropPossible, x: 45, y: 21
But actual coordinates is x: 233, y: 115
Near child:
Drop query child status: DropDestinationQuery, x: 44, y: 21
Drop query canvas status: DropDestinationQuery, x: 44, y: 21
Drag query drag element status: DropSourceQuery, x: 44, y: 21
Drop info canvas status: DropPossible, x: 44, y: 21
Drag info drag element status: DropPossible, x: 44, y: 21
Drop info canvas status: DropImpossible, x: 44, y: 21
Drag info drag element status: DropImpossible, x: 44, y: 21
Drop info canvas status: DropImpossible, x: 44, y: 21
Drop info canvas status: DropImpossible, x: 44, y: 21
Drag info drag element status: DropImpossible, x: 44, y: 21
Drop info canvas status: DropImpossible, x: 44, y: 21
And the second situation: when I have multiple child.
Is this a bug? Or what can I do in this situation?
Thanks, Anatoly.
I have two similar situation:
1) I have a canvas and child controls that is situated by center (i.e.). Canvas and child are allowed drop. When I drag an item I want to get following scenario: First DropQuery event handled by child with, then if the query result is false (or null) - it handled by canvas itself.
But now I have following problems:
a) when I moving over child element and child element set null (or false) to query result I got incorrect RelativeDragPoint for canvas (Their don't change from after child).
b) In the some points (suggest nea border) - I got unnecessary drop impossibel info
c) If child return true for query - why drop quary event handleb on canvas?
Stack trace actions:
With child:
Drop query child status: DropDestinationQuery, x: 45, y: 21
Drop query canvas status: DropDestinationQuery, x: 45, y: 21
Drag query drag element status: DropSourceQuery, x: 45, y: 21
Drop info canvas status: DropPossible, x: 45, y: 21
Drag info drop element status: DropPossible, x: 45, y: 21
But actual coordinates is x: 233, y: 115
Near child:
Drop query child status: DropDestinationQuery, x: 44, y: 21
Drop query canvas status: DropDestinationQuery, x: 44, y: 21
Drag query drag element status: DropSourceQuery, x: 44, y: 21
Drop info canvas status: DropPossible, x: 44, y: 21
Drag info drag element status: DropPossible, x: 44, y: 21
Drop info canvas status: DropImpossible, x: 44, y: 21
Drag info drag element status: DropImpossible, x: 44, y: 21
Drop info canvas status: DropImpossible, x: 44, y: 21
Drop info canvas status: DropImpossible, x: 44, y: 21
Drag info drag element status: DropImpossible, x: 44, y: 21
Drop info canvas status: DropImpossible, x: 44, y: 21
And the second situation: when I have multiple child.
Is this a bug? Or what can I do in this situation?
Thanks, Anatoly.