Well, assuming all you wanted to see was the FSM itself and not what's inside a particular state i can see a system that caches a sort of screen-capture of the FSM and uses that to satisfy this.
though, i would think that it'd get hairy if you wanted to compare the states and actions between two with this kind of system
Hmm... idea... have a system that caches a screenshot of the various FSMs that is independent of the graph view. from there, it caches the general position where the states are... when you click on a state, it then fetches the coordinates from a paired-up file (like a text file or xml or something) and then shows you a screenshot of the actions or just gives you a list of the actions. (i think screenshot would be most flexible since you could see how the actions are configured)
if it's all kept independent and separate and not using the same engine that the graph view uses, it might be possible to implement this without having to worry as much about two graph view windows fighting it out.
