variable sort (on variable tab)

[djaydino]

Hi.

Many times i have lots of variables on a fsm and (for example) i want to look for a Array in the list.



It would speed up the process if you would be able to  sort by name, used or type (by click on Name/Used/Type on top)

[DanielThomas]

+1

[jeanfabre]

Hi,

 I'd like that too indeed!

Bye,

 Jean

[Padenlee]

I always name my variables with a lowercase g, s, f, etc... based on what type it is. Example:

gGameObject
sString
fFloat
ect...

This groups the variables along with the added benefit of allowing me to have similar names like iScore and sScore in the same FSM and makes everything super clean and fast to understand.

I also use other naming conventions like:

vPlayerPos
vPlayerPosFrom
vPlayerPosTo
fPlayerRotY
fPlayerRotYFrom
fPlayerRotYTo
iSpawnCount
iSpawnCountMax
fDist
fPosMult
fPosMultBias
vvSpritePos <--Vector2
etc...

I'm wanting to create a Playmaker Best Practices guide soon. I've been making lists of best practices for the last few months. Along with the few shortcomings with Playmaker I'd suggest changing to make the asset a must have for fast game development. If Playmaker got me on Apple's TV show, it can make people 100k+ a year in app sales. Learning how to do that took me far too many years to discover, I'd like to help others get there much quicker. It would be great if people were able to make a profitable game in 3 months with Playmaker that would normally take a year with C#

[djaydino]

Hi.
@Padenlee

Naming with using a / is much better for grouping, but that is not the point for this request

There is already a type showing, also when you look for a variable on an action it will only show the type you can use or need.

Could you share the shortcomings so PlayMaker can see and maybe adjust or add on a later version?

There is also a best practice wiki page that might be helpful.

[jeanfabre]

Hi,

 that's always good to share your tricks and tips!

I use a lot of signs as well, like $Data which is for example a raw data coming from Xml or json that is not yet parsed, like a string date or something.

 I use _ for private stuff that I want other fsm to be aware of this before messing with private vars.

I actually use plain english names as well, which makes it very clear.

Plenty of small stuff like that make up for a very clear fsm once these rules are adopted widely in your body of work.

 Bye,

 Jean