> "export" the source code back out
>
What do you mean by importing source code to XNA then exporting it out again? That doesn't make any sense. Source code is source code.
As for exporting to source code, I really don't see the point. You would never be able to modify the source code to make changes. The insides of the event engine are very complex, and because there are no languages that support event style picking as language features, the generated sourcecode would not be human readable, it'd just be a massive mess, like a really complicated function copied and pasted a thousand times. And what kind of changes would you make? What would the advantages be? There are no advantages to exporting source code. Only disadvantages.
I disagree. There is no disadvantages of being able to export source code only advantages. I understand it may not be human readable, but even so saying the code as an export would not be useful or have any advantage is a bit extreme and over the top. Code at its very core is better then events, yes I understand events work really really REALLY well in construct, but if the program has a bug or they wish to expand on it with extreme custom code and actions that they could not do within the editor then it would be best to be able to see that code.
I know it will never happen because of how advanced and great the event system is but saying exporting code would not have any advantage is not true in any part of the context. Not trying to call you on anything but facts are facts.
I know the event system can do 99% of what anyone would possibly want with python possibly picking up the slack, but exporting code would be the ultimate in debugging and advanced mechanics.