I'm having behavior problems :)

[Mark Wieder]

Bernard-

Monday, April 13, 2009, 3:24:53 AM, you wrote:

> Maybe I've completely misunderstood things.

No, seems to me you've got it right. My question is more one of "when
is it appropriate to throw a resolutionError message"? In my example,
if I don't have a mouseDoubleUp handler in the script of an image then
it won't respond to mouseDoubleUp clicks. If I put that handler in the
behavior object and assign the behavior then the message is handled.
Now if I delete the behavior object but leave the assignment and then
double-click the mouse what happens?

This gets a bit zen: what's the sound of one mouse doubleclicking?
There's no mouseDoubleUp handler in the image, so how is the engine
supposed to know that I intended to put one in the behavior button?
Isn't this the same situation as an image with no mouseDoubleUp
handler? If I remove the behavior assignment then it is.

The image won't respond to mouseOver events either - should the engine
assume that I meant to put that in the behavior button and give me an
error message?

> BTW, for me it seems that choosing a field would have been a better
> control to contain the script.  It would mean that the field's
> contents could be used for various related information (such as
> documentation).  Again, maybe there's something that makes buttons
> more useful than fields that I am missing.

For that matter, why limit it to any type of object? This question
came up during beta test as well. The rev team likes buttons...

But *do* check out behaviors. IMO this is the best and biggest change
to xtalk programming in years.

-- 
-Mark Wieder
 mwieder at ahsoftware.net