Opened 16 years ago
Closed 9 years ago
#373 closed enhancement (wontfix)
async onDrop
Reported by: | ilia | Owned by: | Eugene Lazutkin |
---|---|---|---|
Priority: | low | Milestone: | future |
Component: | DnD | Version: | 0.2 |
Keywords: | needsreview | Cc: | |
Blocked By: | Blocking: |
Description (last modified by )
Currently I can neither do async drops nor indicate waiting state on drop. That's because DragManager? needs return value from onDrop.
I suggest to change it. onDrop may return
- true => success
- false => failure
- null => DragManager? put into lock state (no dnd available) and wait for async request to return a value and unlock it.
Change History (12)
comment:1 Changed 16 years ago by
Component: | Widgets → DnD |
---|---|
Milestone: | → 0.5 |
comment:2 Changed 16 years ago by
Owner: | changed from anonymous to alex |
---|
No, that refers to an enhancement talk. Reassigning so alex may see.
comment:3 Changed 16 years ago by
Type: | defect → enhancement |
---|
comment:4 Changed 15 years ago by
Owner: | changed from alex to Eugene Lazutkin |
---|---|
Status: | new → assigned |
Sounds like a simple yet useful enhancement.
comment:5 Changed 15 years ago by
Note: probably a source/target should have an additional state, something like "temporary disabled". Such nodes cannot participate in DnD operations, which should be reflected in their appearance.
comment:6 Changed 15 years ago by
Milestone: | 0.9 → 1.0 |
---|
It is useful but rarely asked feature. I am bumping it up to 1.0 release.
comment:7 Changed 15 years ago by
Milestone: | 1.0 → 2.0 |
---|
comment:10 Changed 10 years ago by
Description: | modified (diff) |
---|---|
Keywords: | needsreview added |
Priority: | high → low |
comment:11 Changed 9 years ago by
This is the oldest open Dojo ticket.
Either we should implement this, or close it out.
comment:12 Changed 9 years ago by
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
This ticket will be a candidate for 2.0.
still a bug?