I am just reporting back on what I have found so far in case anybody else finds them self in the same situation

View objects that are clickable receive mouse events and view objects that are not clickable do not receive mouse events.

Adding an mouse event handler to an object by setting a mouse event handler attribute or by adding a method specifically designated to handle the event sets the clickable attribute of the object to true.So...

<view onmousedown='Debug.write("received mousedown")'></view>

and

<view>
 Debug.write("received mousedown");
</view>

both have the side effect of setting the clickable attribute of the view to true.

This is appears to be the case for the following handlers:onmousedown, onmouseup, onmouseover,onmouseout, and onclick.

A views clickable attribute affects how mouse events are propagated to the underlying flash movie clip. One effect this has is that text selection for clickable inputtext fields does not work correctly. This seems to be a bug, but I am not sure. I am still trying to figure out exactly what is going on in the code for LzView.prototype.setClickable.

Does anyone know if the above behavior is a bug or is the intended behavior. I think it should either be documented or changed so I guess I want to either file a bug against the docs or against LFC.

Also for my problem I do have a workaround.involving LzGlobalMouse which reports mouse up and down even when the mouse is over a non-clickable field.

Thanks,
Daniel.
_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user

Reply via email to