At 4:25 PM +0200 14/10/1999, Eva Isotalo wrote:
>This worked fine. Another problem arised though. Typical.. :o(
>
>I have palette windows where an image of something I "carry" is
>shown. A 'mouseDown' in the background of this image closes the
>palette window and shows the 'real' image at the mouseloc. This
>'real' image can be moved around emidiately (no mouseUp after the
>mousedown on the palette window). But with this new script, the
>'real' image shows up at the mouseloc but can't be move emidiately,
>only after a new mouseDown.
>
>From the palette window a 'send "mouseDown" to image "boot"' is sent.
>
>I have approx. 300 images with different behavior in different
>situations. Since I'm a "self learned programmer" I can't figure out
>how to fix this situation since I don't understand why using the
>local variable is working so well. ??? And why is the 'send' not
>working with this new script.
I'm not sure if I understand the problem, but ...
Are the handlers that control the movement of the image in the script
of the image (mouseDown, mouseMove, mouseUp)? If so, "sending" the
mouseDown to the image won't produce the other messages you get with
a real click. Instead of sending a mouseDown message, could you send
another message?
For example, in the palette:
on mouseDown
--close stack or whatever
send "myMessage" to image "boot"
end mouseDown
In the image:
on myMessage
if the mouse is down then
set the loc of me to the mouseLoc --or whatever
send "myMessage' to me in 5 milliseconds
end if
end myMessage
Cheers
Dave Cragg
_____________________________________________
The LACS Centre (Business English Training Resources)
mailto:[EMAIL PROTECTED]
http://www.lacscentre.co.uk
_____________________________________________
