![]() |
|
|||||||
| Programming with Objects User to user discussions about programming with objects, including COM objects. |
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
Events documentation
I don't understand this bit of the documentation about EVENTS:
Quote:
|
|
#2
|
|||
|
|||
|
Haven't read it, but can't help but believe its a typo.
__________________
Fred "fharris"+Chr$(64)+"evenlink"+Chr$(46)+"com" |
|
#3
|
|||
|
|||
|
Subscription = EVENTS FROM oMath CALL oStatus
Cancel subscription = EVENTS END oStatus See Event Source in the Docs. Edit: Might be useful to look at differently. One object uses RAISEEVENT to send a notice. Who gets that notice? Everyone that issued an EVENTS FROM ..., at least until they issue an EVENTS END. Reedit: Also from the docs "32 concurrent client subscribers ". I.e. EVENTS FROM could be issued for up to 32 different objects. If 32 objects had an EVENTS FROM issued for them, when the server issued a raise event, it would send the event to all 32 objects (the subscribers). Think of a newspaper or magazine subscription, very, very similar. Last edited by Larry Charlton; Mar 20th, 2012 at 02:44 PM. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|