As I understand it, in Signals, it's related to the mechanisms to handle signal 
payloads. In other words, data or object pointers you can dispatch from a 
signal and receive in a listener function elsewhere. It makes it really easy - 
you just declare a signal dispatches a certain kind of object (like a value 
object that holds data) and then you can then add that in the argument of the 
listener function.  

For example, in with regular AS3 events, you write a handler like this:

   onMyEvent(event:SomeEvent):void {}

but in signals, it's not the event/signal itself that is declared in the 
function arguments, but the signal's payload, whatever that is:

   onMySignal(myDataVO:MyDataVO):void {}

That's my understanding anyway.  I know very little about how slots are done in 
C#, only from what I have read. 


 Jason Merrill
 Instructional Technology Architect II
 Bank of America  Global Learning 





_______________________


-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Kevin Newman
Sent: Thursday, December 01, 2011 2:44 PM
To: Flash Coders List
Subject: [Flashcoders] Value of AS3 Signals Slot system

Hi all,

I've been looking into AS3 Signals and wanted to run something by everyone that 
I can't figure out. What is the value of the Slot system in the AS3 Signals 
toolset?

It seems like a lot of overhead, and I'm not sure what it brings to the table. 
Am I just too dense to see it (likely)?

Kevin N.

_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the 
intended recipient(s) and may contain information that is privileged, 
confidential or proprietary. If you are not an intended recipient, please 
notify the sender, and then please delete and destroy all copies and 
attachments, and be advised that any review or dissemination of, or the taking 
of any action in reliance on, the information contained in or attached to this 
message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a 
solicitation of any investment products or other financial product or service, 
an official confirmation of any transaction, or an official statement of 
Sender. Subject to applicable law, Sender may intercept, monitor, review and 
retain e-communications (EC) traveling through its networks/systems and may 
produce any such EC to regulators, law enforcement, in litigation and as 
required by law. 
The laws of the country of each sender/recipient may impact the handling of EC, 
and EC may be archived, supervised and produced in countries other than the 
country in which you are located. This message cannot be guaranteed to be 
secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of America 
Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are 
Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a 
Condition to Any Banking Service or Activity * Are Not Insured by Any Federal 
Government Agency. Attachments that are part of this EC may have additional 
important disclosures and disclaimers, which you should read. This message is 
subject to terms available at the following link: 
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you 
consent to the foregoing.
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Reply via email to