Morphic event-handling confusion

>I'm trying to use Morphic, in Squeak 3.9, to make a very simple "physics
>model" I call a HockeyPuck. The idea is that it's a CircleMorph subclass
>that one should be able to pick up with the Hand and "throw", and have
>it bounce off the World edge (and then, hopefully, other such Pucks).
>I've got the "step" animation thing figured out pretty well, and I have
>some idea how to compute the motion and bounces and such, but I'm
>stumped as to how to properly handle the mouse events. On Eddie
>Cottongim's suggestion, at http://wiki.squeak.org/squeak/2477 , I tried
>using  "self on: #startDrag send: #beginThrow to: self" (in my
>initialize method) but that seems a little weird, and doesn't seem to
>allow the default dragging behavior to go through. I also tried the
>approach of overriding handlesMouseDown and mouseDown, and sending
>"super mouseDown" in the latter, but that doesn't seem to work any
>better, although it makes a little more sense to me.
>
>There's a two-step sequence of messages I'd like my Puck to receive
>while still doing the normal getting-moved-by-the-Hand stuff. The first
>is #beginThrow, to be sent either on a mouseDown or (preferably) on a
>startDrag event. The second is #endThrow, to be sent on the subsequent
>mouseUp. How can I make this happen?
>  
>

>  
>
>>handlesMouseStillDown: evt
>>    ^ true
>>
>>mouseStillDown: evt
>>    self position: evt hand position.
>>    
>>
>
>These apparently don't do anything. But, that's OK, because I can, as
>Bert suggested, just send "evt hand #grabMorph: self".
>
>Except, oops, that's NOT OK, because now mouseUp: apparently never gets
>sent to my Morph.
>
>So, I still need help. Thank you both very much.
>  
>

They "worked for me" - I was dragging a Morph around, and had readouts

> Thanks, I already got it working, which was in fact a very  
> satisfying experience. My previous failure was using a  
> "handlesMousedown" method, rather than "handlesMouseDown:evt"  
> method. An important distinction.
>
> Sent via BlackBerry from T-Mobile
>
> -----Original Message-----
> From: Michael van der Gulik <[hidden email]>
> Date: Sat, 17 Mar 2007 17:45:07
> To:"A friendly place to get answers to even the most basic  
> questions aboutSqueak." <[hidden email]>
> Subject: Re: [Newbies] Morphic event-handling confusion
>
> Max OrHai wrote:
>
>>
>>
>>> handlesMouseStillDown: evt
>>>    ^ true
>>>
>>> mouseStillDown: evt
>>>    self position: evt hand position.
>>>
>>>
>>
>> These apparently don't do anything. But, that's OK, because I can, as
>> Bert suggested, just send "evt hand #grabMorph: self".
>>
>> Except, oops, that's NOT OK, because now mouseUp: apparently never  
>> gets
>> sent to my Morph.
>>
>> So, I still need help. Thank you both very much.
>>
>>
> They "worked for me" - I was dragging a Morph around, and had readouts
> for the start and end positions of the dragging. Try making a  
> completely
> fresh subclass of Morph with only the methods I suggested. I used  
> Squeak
> 3.9.
>
> If I was going to implement momentum, I'd take the current position on
> mouseUp: and the position received by the very latest mouseStillDown:,
> and work out which vector the puck should travel in from that. I  
> suppose
> you'd also need the times of those two events as well to calculate the
> velocity vector.
>
> Michael.
> _______________________________________________
> Beginners mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>
> _______________________________________________
> Beginners mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/beginners