Hello,
I am trying to allow the use of cel expressions in triggers as was previously
suggested on this list as a useful feature to hopefully be implemented as part
of the quest refactor. However, having succesfully implementing this yesterday
in sequences and seqops I am struggling to do this in triggers.
The celExpressionParameter's Get method requires a celParameterBlock be passed
as an argument, that is then passed onto the iCelExpression execute method. A
celParameterBlock is an optional argument to this method, but certain
expressions query, and therefore need, the parameter block.
Triggers pass a parameter block to methods registered for callback when they
fire. So this parameter block can be passed to rewards allowing the use of
expressions there (as previously available) and subsequently can be passed on
by the reward start sequence and used inside sequences and seqops (as now
available).
However, my complication comes from and my query is, how can we make use of
celExpressionParameter's inside triggers when they require a celParameterBlock
that is often not populated until the trigger fires?
Thank you to anyone who has the time to consider this issue.
Kind Regards, Sam
_________________________________________________________________
Windows Live Messenger: Celebrate 10 amazing years with free winks and
emoticons.
http://clk.atdmt.com/UKM/go/157562755/direct/01/
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Cel-main mailing list
Cel-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cel-main
