On Wed, Jul 8, 2009 at 3:04 PM, Michael Rueger
<m.rueger@acm.org> wrote:
Mariano Martinez Peck wrote:
> This is strange because it is interpreted as if it were a DropFilesEvent!
>
> But this is just a alt + tab. I don't see the relation between and alt +
> tab and a DropFilesEvent
could be some oddness in the Windows event generation/handling.
A fix would be to check for a nil file entry in the drop event in
ExternalDropHandler class>>lookupExternalDropHandler:
But I think that's not the real problem, just a fix. I am right?
What I can see debugging is that HandMorph>>processEvents
when it does: Sensor nextEvent
that returns: #(3 11623748 4 0 0 0 1 1)
which 3 means type EventTypeDragDropFiles...
but I wonder why Sensor nextEvent is returning me that in and "alt + tab".
best,
Mariano
�
Michael