playMaker

Author Topic: FsmList - For storing Lists of varying datatypes  (Read 4216 times)

Disastercake

  • Full Member
  • ***
  • Posts: 101
  • www.disastercake.com
    • Disastercake
FsmList - For storing Lists of varying datatypes
« on: June 07, 2012, 11:02:36 PM »
I would find it extremely useful if there was an FsmList class that could store lists of different datatypes.  Preferably it would have more of a list functionality, and not a simple array.  The lack of lists makes me have to write custom components and attach them to different game objects but Lists in Playmaker would make it easier for me to stay within Playmaker.
Soul Saga - Anime themed adventure RPG by Disastercake

http://www.disastercake.com

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15500
  • Official Playmaker Support
Re: FsmList - For storing Lists of varying datatypes
« Reply #1 on: June 08, 2012, 06:18:41 AM »
Hi,

 ArrayMaker to the rescue!

https://hutonggames.fogbugz.com/default.asp?W715

You can work with lists and hashtables and it feature a complete integrationg of all functions that deals with arrays and list.

 Le me know if you need a head start, but the examples are pretty simply and since you are already using playmaker, working with arrayMaker will be just fine.

Bye,

 Jean

Disastercake

  • Full Member
  • ***
  • Posts: 101
  • www.disastercake.com
    • Disastercake
Re: FsmList - For storing Lists of varying datatypes
« Reply #2 on: June 08, 2012, 10:55:18 AM »
Sweet!  Thanks for the heads up. =)  Why isn't this automatically included in the package, though?
Soul Saga - Anime themed adventure RPG by Disastercake

http://www.disastercake.com

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15500
  • Official Playmaker Support
Re: FsmList - For storing Lists of varying datatypes
« Reply #3 on: June 08, 2012, 01:59:10 PM »
Hi,

 a proper integration of such listing system would be very complex I think, because of the implication in almost all actions interfaces and likely also internaly. The solution I came up with is ok-ish, I did the best I could, but it's definitely not ideal, for example the actions interface is too long because of the lack of ui to let the user select a type of variable and then the variable reference. Laos I can't really provide a way to let the user define any type for the hashtable key so I had to constraint to string, else the action interface would be one meter long...:), so having a built in system means a lot of work, and then exceptions would be to handle database, xml, and all them other types of data management.

 Bye,

 Jean