The way the expression parser currently works, the first argument is assumed to
be a property and is automatically evaluated. The second argument is assumed
not to be a property and is not evaluated. However, you can use the $name$
syntax in property expressions to force the evaluation of a property prior to
the match being done. So what you want to use is:
TP > $TN$
My current project is to use the Java Expression Parser (JEP) to parse and
evaluate Property Match expressions, as well as a new 'Calculated Proprty'
trait which will allow you to enter an arbitrarily complex matchematical
formula using property values.
This is going well. The tricky bit is that Property Match Expressions (PME's)
are not currently well formed and the format of them is going to have to change
(mainly quoting strings). There will be a one-off auto-conversion of existing
PME's to the new layout when you first use the updated VASSAL.
Cheers,
Brent.
>*********** REPLY SEPARATOR ***********
>
>On 30/09/2006 at 10:44 PM carrington_ward wrote:
>Doesn't work, I take it....
>
>Am I correct that I can't set up a trigger TP > PN where TP and PN are
>both properties?
>
>
____________________________________________________________
Brent Easton
Analyst/Programmer
University of Western Sydney
Email: [EMAIL PROTECTED]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/vassalengine/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/vassalengine/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
