A few suggestions to add to the workflow extension:
I use these in my extension blocks :
- set [ game_attribute] to [ value ] PURPLE or set public [ ] to [ value ]
it is still better than the [ set game attribute with name [ ] to [ ] ]
- get [ game_attribute ] PURPLE
- [null]
There is [empty] but that is only for map,lists . When you have a variable like image it is hard to know if it is set or not. Also checking for null rather than the approriate block is empty, has value etc.. is more direct. Granted : you need more programming background to know how use it.
- [ condintion ] ? [ true ] : [false ]
when you want to set a value for instance [ set X to [ y = 2 ] ? 3 : 2 ] Now you need to do this:
if [ y = 2 ]
set X to 3;
otherwise
set X to 2;
You could make this block using your own method of combining the condition elements. Not sure if it would need to allow AND , OR since that would make the block harder to make.
(or mabye more difficult to make: a [>] icon to click on with the default to automatically add a & [ ] Now you need to copy / paste text )
- get scale width/height of [Actor]
actor.realScaleX and actor.realScaleY : to get the scaling width/height after you used the grow block
- set name from [Actor] to []
- get actor name of [Actor]
- get actor by name []
set / get Actor Name in combination with [ get Actor by name [] ]
get = [actor.name] , set = [actor.name=“abc”;] You have get actor type by name but it would be easier to reference a particular actor instead of the [for each type of actor ] block to get just one actor who you know exist only once .
- DateTools.format(Date.now(),"%Y-%m-%d_%H:%M:%S”)
Put this in draw block on scene draw event and you see nice clock
You can get wild with blocks on this one ) Maybe one for date and one for time and one for both?
A little more obscure = not needed much and more difficult to maintain:
- set origin point of animation to [ center, top, etc.. ]
It would be awesome to have these workflow blocks in a default extension or implemented in Stencyl. I have the upmost confidence that the core developers know how to maintain them.
Important:Maybe the biggest reason not to implement the [<,>,=] and [+,- etc.] : When you click in a block you can change this and lead to logic-bugs that are hard to spot later. So that might be a reason not to change the core-blocks and have them as seperate blocks to be used or not.
Best regards from
M.E.
