Idea for organization of larger works.

[BrandonC]

So I'm making a game, and already the engine is a good hefty 200+ events. So heres the problem, and I'd love for someone to give me an easy solution, but until then I'm making this in the form of a request.
See, I made the entire engine to collide with Backdrops, only to find out that if I wanted moving platforms and such, that I would actually need to use Active Objects too. So I made an active object, and all my platform based active objects are going to use the "Neutral" Qualifier. Now I need to go into this huge engine and add in copies of all of them.

The problem isn't so much there, but more so the fact that. If this was a specific "Collide with Object", all I would have to do is click on the object at the top, and it would only show events with that object. Narrowing down 85% of my entire engine down to just those events, most of which are collision events.
However, theres no way to do this with Backdrops, and I have a bunch of sensors that all need to collide with the Backdrops, so I can't just go and click on each sensor and check for events, it would be a pain.

So my request is, perhaps have a special show/hide for events that work with backdrops.

[pinacoladaxb]

That is a really good idea. As for your problem, I am reeeeally sorry. Just spend some time going through the events and pretend it's a game. If you convince yourself you're having fun doing something that frustrating, you'll get through it much faster and easier.

[BrandonC]

In addition to this idea, perhaps we could have:
Most recently edited events.
Perhaps an optional number that shows what we changed, so we don't keep clicking Undo and Redo to debug our code in very complex situations.

And an option that allows for a "Smooth" scroll in the event editor.

Is it obvious yet, that I'm having difficult times dealing with my current project?

[RayMarble]

... Most recently edited events.
Perhaps an optional number that shows what we changed, so we don't keep clicking Undo and Redo to debug our code in very complex situations...

You mean like the history window in Photoshop? (For people that don't use it, basically it shows the list of last actions and one can selectively roll back - I guess in this case a picture is really worth more than a descripton: http://i28.tinypic.com/2vmg5fk.jpg)?

[BrandonC]

Yes, a lot like that. However, it wouldn't just be a list of undos. It would be sort of like "Arrange By Date" in Windows Explorer.

Of course, you would need some sort of notification that says "Not runtime order." so that people know that it's a modified arrangement, and not actually the order for which events are being run.
Which is why rather then doing arrangements, you could do something like a number or a color coding, like perhaps events with a red background are the most recently added. Orange for the event just before that, Yellow before that, so on. And for events that were MODIFIED and not created, a Red outline.