ragamer
March 20th, 2010, 15:22
The situation is the following. The chatwindow is basically the central nexus of information on a session as everyone shows rolls, add results, comments, etc, etc...
...The problem I have is that I want to make the drags you get from it "smarter" so specific drags can ONLY go to specific controls in the rest of my windows.
My plan was analyzing the string format of the message description to alter its type.
The problem I'm finding is the following:
When the control is the chatwindow:
When you inititate a drag operation, onDrag() is called BUT Input.getDragData() returns nil. Which, according to the documentation should mean that no drag'n drop operation is active (which is obviously not the case).
On ANY other control:
When you initiate a drag operation, onDrag() is called, and when you call Input.getDragData() you get a valid dragdata object that you can process and alter to trigger all kind of fancy operations/behaviours.
The other difference is that OnDrag() coming from any control but the chatwindow is called multiple times over the "move" (as the documentation specifically states)... On the chatwindow happens only once.
So is the documentation about Input wrong? Or is this another end-road I met because the "chatwindow" is special and is not really inheriting the properties of "windowcontrol" object? A bug? I'm missing something else?
...The problem I have is that I want to make the drags you get from it "smarter" so specific drags can ONLY go to specific controls in the rest of my windows.
My plan was analyzing the string format of the message description to alter its type.
The problem I'm finding is the following:
When the control is the chatwindow:
When you inititate a drag operation, onDrag() is called BUT Input.getDragData() returns nil. Which, according to the documentation should mean that no drag'n drop operation is active (which is obviously not the case).
On ANY other control:
When you initiate a drag operation, onDrag() is called, and when you call Input.getDragData() you get a valid dragdata object that you can process and alter to trigger all kind of fancy operations/behaviours.
The other difference is that OnDrag() coming from any control but the chatwindow is called multiple times over the "move" (as the documentation specifically states)... On the chatwindow happens only once.
So is the documentation about Input wrong? Or is this another end-road I met because the "chatwindow" is special and is not really inheriting the properties of "windowcontrol" object? A bug? I'm missing something else?