I've got a lot of code consolidated into #includes because I'm hurriedly rebuilding about 10 different flash games with a lot of shared functionality has was, previously, tossed harem-scarem all over the FLAs of the games. The company we had coding them did the most abyssmal job I've ever seen. Flash 4 games had better code flow. The AS2 classes that the games use are such a mess in every conceiveable way that the only way we can get these games ready in time for our deadlines is to leave as much of the original code in place as possible, and just fix bugs.
Building classes for the code in the #includes that made any kind of sense would mean drastic restructuring of everything else. And the code base is ridiculously gigantic. So we're stuck. Currently, though, it seems ASDT has decided to stop compiling on save altogether, so I'm up an additional creek. My new AS2 Project won't run MTASC, and my old one still will. -Mark Hawley --------------------------- Martin wrote: hmm, #included you say.. nothing that i know of, can you show an example of what you are doing, im curious as to why you would be doing an include rather than an import. (not that its wrong or anything, just curious :) John Mark Hawley wrote: <snipped> -- John Mark Hawley The Nilbog Group 773.968.4980 (cell) _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
