Morphic error

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Morphic error

Marcus Pedersén
Hi!
I have made a small app with buttons, textfields and a "clock".
Quite often I get an error that says that one of my morphs  
( different morphs from time to time) do not handle mouseOver: evt.
I am suspecting that I updates my different morphs with same type of  
message. World doOneCycleNow is the problem. For instance I update my  
clock with World doOneCycleNow every second.
Is there a better way to just update a specific morph?
Or am I on the wrong track with my error, is there something else  
that can make my GUI throw this exception?
Please help me on where to start looking!
Many thanks in advance!
Regards
Marcus

Reply | Threaded
Open this post in threaded view
|

Re: Morphic error

Michaël Piel
On Mon, 20 Mar 2006 22:41:28 +0100
Marcus Pedersén <[hidden email]> wrote:

> Hi!
> I have made a small app with buttons, textfields and a "clock".
> Quite often I get an error that says that one of my morphs  
> ( different morphs from time to time) do not handle mouseOver: evt.
> I am suspecting that I updates my different morphs with same type of  
> message. World doOneCycleNow is the problem. For instance I update my  
> clock with World doOneCycleNow every second.
> Is there a better way to just update a specific morph?

You can use the #step and #stepTime (in milliseconds) methods from Morph. I guess you subclassed (something)Morph for your clock. So you just have to redefine these 2 methods.

> Or am I on the wrong track with my error, is there something else  
> that can make my GUI throw this exception?
> Please help me on where to start looking!
> Many thanks in advance!
> Regards
> Marcus
>