I would seem to have a knack for not remembering I am still in play mode while making changes to FS, BT and FSMs. Is there a way to keep one’s changes while in play mode? It would allow me to continue to make my mistaken attempts at making changes but without loosing all of my work once I realize my mistake.
There is -at least currently- no real way to retain the changes made in play mode back to when exiting play mode. This feature has though been requested in the past more than once, so I will take a look at this once after FlowCanvas v2 is out, which is pretty soon actually! 🙂
Woot, woot! Yeah, don’t let me slow you down. I am super happy with my purchase, knowing that you’re working on v2 makes me smile even more. I have thought about making a similar nodal interface for a website builder project I worked on a while back. Seeing FlowCanvas in action warms my heart.
I thought macros did it for a bit, but now that I reset my Preferred Type list the behavior seems to be gone. I was also not seeing the updates to the Preferred Type list until I reloaded the project, another indication it was corrupted. My guess is I referenced something then removed what was referenced. Does that sound like something that’d do it to you?
Thanks once again for your positive feedback!
There is indeed a small bug in the Preferred Types not refreshing unless, either restarting Unity, or better yet, entering-exiting playmode.
This bug has of course been fixed for the new version coming around! 🙂
Hi. My Solution For this currently is pretty simplistic, but works quite well in most cases :
During Playmode, I Export a graph to a json-file ( just some dummyfile for temporary saving of graphs ) .
On the Graph – Import that temporary-JSON-File into the graph again.
Maybe one could provide a button or a tickmark for the graph, which would allow us while being in playmode to mark those graphsm, which we want this to happen automatically ( like : “persist Changes after Playmode” or something) . I think it probably wouldn’t be too difficult to implement this autosaving and loading ? Would still be quite useful I think ..
I’ve also had problems with my setup that I believe is related to the no-save system. When I instantiate FlowScript during runtime for my custom script driver, any changes to the FlowScript asset do not take effect even when I re-instantiate the FlowScript Asset.
Probably a check/mark/button like @dave suggests could actually be implemented easily (I need to re-check all occasions), which in essence will just do what @dave already does manually, but instead do so automatically.