No, it should be changed to not use Sensor directly.

- Bert -

On 22.12.2008, at 00:12, karl ramberg wrote:

> So maybe the TransferMorph>>step should have a 'self  delete' if owner
> is not a hand morph? Or is there cases where transferMorphs live by
> them self ?
>
> Karl
>
> On 12/21/08, Bert Freudenberg <bert at freudenbergs.de> wrote:
>>
>> On 21.12.2008, at 21:06, Julian Fitzell wrote:
>>
>>> On Sun, Dec 21, 2008 at 8:38 PM, Andreas Raab <andreas.raab at gmx.de>
>>> wrote:
>>>> Julian Fitzell wrote:
>>>>>
>>>>> Did anybody ever figure out what the heck is causing this? It's
>>>>> driving me nuts!!
>>>>
>>>> It's users of Sensor>>mouseButtons, Sensor>>shiftPressed etc. The
>>>> main
>>>> suspect in this regard is TransferMorph which does this:
>>>>
>>>> TransferMorph>>step
>>>>      self shouldCopy: Sensor shiftPressed.
>>>>      self updateCopyIcon
>>>>
>>>> A lingering TransforMorph (which can happen after DnD errors) will
>>>> happily
>>>> eat all your events.
>>>
>>> Thank you, thank you, thank you. This fixed it:
>>>
>>> TransferMorph allInstances do: [:ea | ea delete]
>>>
>>> (there was a lingering one - it had an omnibrowser method node as a
>>> passenger)
>>>
>>> Not sure why this is happening so much to me right now but at  
>>> least I
>>> have a fix.
>>
>>
>> Oh great! We have encountered this from time to time but never got
>> down to the cause. Thanks Andreas!
>>
>> - Bert -
>>
>>
>>
>>
>