Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Report Listener Strategy?
Message
From
16/09/2008 14:23:26
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Title:
Report Listener Strategy?
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows XP SP2
Network:
Windows 2008 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01348000
Message ID:
01348000
Views:
45
I'm just now seriously getting into using report listeners. Have read
the excellent writeups by Cathy Pountney, Doug Hennig, the
Nichollses and others. I would like to know if the following
approach to implementing listeners could create potential problems:

(1) Add an oLeadListener property to my abstract listener class.

(2) In the Init, set oLeadListener = This and have an assign
method that propagates the reference to all of the successor
listeners in the chain.

(3) Any pre- Render and post-Render changes done by the lead
and/or the successor listeners are implemented on the lead listener.

(4) The lead listener's Render is the one that is called. Add an
lRender switch to the abstract listener class in case there is
ever a situation where a different (or more than one) listener's
Render needs to be called.

Seems to me that would be a simpler approach than trying to
make sure that everything is properly shared by propagating
downward through the successor chain.
Reply
Map
View

Click here to load this message in the networking platform