I'm still using .62 so if this has already been added, please forgive me:
-Ability to lasso any number of events... then copy and paste them into other layouts.
-This one is nuts... ability to export and then send and receive single layouts between developers, so that you can easily create development teams where everyone can work on one part of the game without having to wait for someone to finish and pass the file around. Then the team leader can receive all layouts and then be able to place those layouts into the main project file.
-Here is another crazy one... how about a feature that lets you tilt things in a 3D-type space like Google Sketchup. It would need to of course maintain a higher picture quality, but think of the possibilities of being able to program events that made the tilt change position and direction based on how the character moves.
New objects that handle popular video game features...
-Custom music track object... This would allow gamers to add their own custom music into the game themselves by selecting it in a game menu and then searching his/her hard drive, and saving the music into the gamesave file. It should be event-based meaning that the programmer can leave it open to the gamer to set the music for any number of -in-game events that the programmer has left open. For example, music that plays for each level, when a player dies, when a player clears a level, finds an item, etc, etc... whatever the programmer leaves open, the gamer can add custom music for it.
*More robust loading capabilities that will not only load objects, sounds, and sprites in other layouts (i.e. you're in layout 1 and it starts loading everything in layout 2), but also gives you visual feedback that it's loading and let's you know when it's fully loaded (with the feedback being able to be turned on or off optionally by the programmer).
*Layout Replay feature- this would be great for sports games. The featute would allow you to set it to where it will replay what just happened in the layout automatically (auto-replay) or by the user pressing a button to call up hiw own replay (user replay), all of which would adhering to the angle, position, speed, camera on sprite, with or without audo from that layout... and the programmer can set the beginning and ending points (i.e., I could set it to where the replay plays only from the point where the ball was kicked, and stops when the ball hits the net or goes out of bounds, etc).
User Button mapping- This would let the gamer easily reconfigure the button commands the programmer has set.