Hi,
Sorry for the wait, trying to keep up
Please find attached a working sample working on Unity 4.
-- you have a book list with prices
-- the PlayMaker inspector shows min and max price and a search button, click on search
-- the fsm deselect all books ( all children, and send the event "DESELECT")
-- the fsm filters the books given that price range
-- then it goes trhough each filtered book and select them ( send event "SELECT)
so with this you have everything to start building a listing that you can enable or disable.
IF you plan on disabling gameobject, make sure you keep them into an Array ( using ArrayMaker), cause disabled gameobject can't be searched withint he hierarchy.
one possible improvment here is to populate the books using xml, here I went to the point and created them by hand with just their id, but really they should be popluated with an fsm that feature all the xml data as fsm variables.
Let me know if this helps.
I don't put this on the ecosystem, I want PlayMaker 1.8 to be out first and clean up the existing samples.
Bye,
Jean