Playmaker Updates & Downloads > Official Action Updates

Conditional Expression Action (BETA)

(1/9) > >>

Alex Chouls:
First a huge thanks to Lea Hayes for doing all the hard work on this action!!

The Conditional Expression action lets you evaluate an expression as true or false and store the result or send events based on the result.

You can use named FSM variables in the expression. If the variable name has spaces use this format: $(variable name with spaces)

Anyway, have a play with it and post feedback. This should be considered a beta release. The final version will be included in the next update.

And again, a huge thanks to Lea Hayes for contributing this action to Playmaker!
Lea makes the excellent Rotorz Tile System: http://u3d.as/content/rotorz-limited/rotorz-tile-system/2UU
He also has a great blog: http://leahayes.wordpress.com/
And Rotorz blog: http://rotorz.com/blog/

EDIT: Updated to v1.1:
- Made text field bigger.
- Added Refresh button.

Some sort of auto-refresh is preferable, but it will need editor support, so for now there is a manual refresh button for when you add/remove/edit variables and then return to the action.

EDIT: Fixed build error.

TrentSterling:
 :o oWoow

EDIT: I like seeing programmer centric actions. Being able to evaluate little bits of code like this might not be strictly 'playmaker style', but it would really cut down on action clutter and it's quite awesome!

And I'm also happy I avoid spaces in my variable names now :)

Lane:
Awesome!  ;D

1) First thing I would suggest is a bigger space to type the expression =) Like the comment action field has.

2) Also during the editor mode you have to actually click and change the expression field if you want it to re-evaluate any variable changes you've made in the editor.

jeanfabre:
Hi,

 Very cool, I would see straight away a lot of thing to expand on this.

 expression should allow the return of more than a bool, floats, ints, string, etc. I feel it could be frustrating to get such a convenient action to just return bools, but I am not sure how it's made under the hood, so it may be not really possible to expand on this.

also, I tried to use a string variable but I think the value will always evaluate to true, I think it should evaluate string for "1", "true" "false", empty or with content and return true or false on these cases.

Or, maybe double check what variables are use and warn the user about unsupported variable types within this expression

Bye,

 Jean

Alex Chouls:

--- Quote from: Lane on May 17, 2014, 10:19:42 AM ---Awesome!  ;D

1) First thing I would suggest is a bigger space to type the expression =) Like the comment action field has.

2) Also during the editor mode you have to actually click and change the expression field if you want it to re-evaluate any variable changes you've made in the editor.

--- End quote ---

Great feedback! I've uploaded v1.1 above...

Navigation

[0] Message Index

[#] Next page

Go to full version