[Laszlo-dev] Generic notifying events [Was: For Review: Change 20090427-hqm-Q Summary: fix for swf9 context menus, mouseEnabled no longer always set to true on every sprite]

P T Withington ptw at pobox.com
Tue Apr 28 14:01:45 PDT 2009


On 2009-04-28, at 16:38EDT, Max Carlson wrote:

> P T Withington wrote:
>> On 2009-04-28, at 16:16EDT, Max Carlson wrote:
>>>> So all you have to do is make your own declared event instance to  
>>>> initialize your event to, you don't have to make a separate class.
>>>
>>> How would this work in declarative syntax?
>> Give me an example of where you would need it and I will tell you.   
>> The only places I could think of using this is internally when  
>> connecting events to the runtime, because the runtime only accepts  
>> callbacks and you would like to not register a callback that is  
>> going to be a no-op because the corresponding event is not ready.   
>> In declarative code, setAttribute is already optimized to do  
>> nothing if the corresponding event is not ready.
>
> I guess this isn't directly related to generic notifying events, but  
> IWBRN if the webtop team could subclass events to store extra values  
> a la closures.

You want: http://jira.openlaszlo.org/jira/browse/LPP-6034

> They would also like to be able to prevent cascading events for  
> custom events where the value hasn't changed.  This should all be  
> possible in script, but perhaps there should be a way to tell <event/ 
> > to use a subclass of lz.Event.

Not sure what you mean here, this sounds like what http://jira.openlaszlo.org/jira/browse/LPP-8058 
  already did.


More information about the Laszlo-dev mailing list