Sean P. DeNigris wrote
> Maybe it should be moved?
Ouch! #acceptDroppingMorph:event: was the message I really wanted, but it
was in the 'layout' protocol! That's just mean ;)
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Custom-DND-Drop-Action-tp4803667p4803724.html
Peter Uhnák wrote
> at least from my naive view it should belong to both (and
> protocols don't work like tags).
I agree. Maybe that will be Pharo's next fun enhancement!
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Custom-DND-Drop-Action-tp4803667p4803694.html
Sen
On Wed, Feb 4, 2015 at 5:53 PM, Sean P. DeNigris
wrote:
> Never mind. I found #handleDropMorph:, which I missed the first time
> because
>
Thanks! You saved me a search. :)
> it is not in the dropping/grabbing protocol, but is instead in
> events-processing. Maybe it should be moved?
This is m
Never mind. I found #handleDropMorph:, which I missed the first time because
it is not in the dropping/grabbing protocol, but is instead in
events-processing. Maybe it should be moved?
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Custom-DND-Drop-Action-tp4803667p480
How do I accept a dropped Morph, but do something other than the default
add-as-submorph? I want to drop a Morph into a TextMorph and have it be
automatically converted into a TextAnchor, but instead it becomes a submorph
and takes over all available space so the contents of the TextMorph can not
b
