Do you use Projects?

Is there an advantage to using a project? For instance, if I were to split my MFA up into several, and tie them all together into a project, would that make version control via Git or SVN more feasible?

discovered today :o hm, that might work with some kind of version control or like workspaces: where app1 is game, app2 is level editor app3 for testring new features so on...

That's what I was thinking. You'd still have to tie everything back together manually, but it would be a lot easier for, say, letting one team member work on the game, one team member work on the menu, etc. As long as the individual MFA's are checked out and back in, I don't think it'd be too big a hassle. The only issue might come in with Jump to Frame, where you paste a checked-in frame back into the main MFA and then suddenly your code tells you that frame is missing, but that could probably be avoided by doing frame changes as a calculation rather than manually selecting the frame to jump to.

Or I suppose you could run the top-level application as one big, complex sub-app that always pulls from the updated MFA's...

I've never once considered it until this thread. Not sure about the application, but I do use two separate MFAs to build my current game. Still, because individual MFAs aren't updated in the project if you save a new iteration of the mfa and not the project containing it, it seems like more hassle than it's worth.

I just updated my game yesterday to use a project. I've got one MFA that's kind of the parent project, and contains the individual frames, also saved out as separate MFA's. Then ideally I can copy/paste the frames from the child MFA's into the parent when they're ready, and in so doing, ideally not damage anything else in the game, and make the project more manageable when I get multiple people working on it. We'll see, but I do wish I could link MFA's in a project like individual frames.