There doesn't appear to be anything describing this in the help files. Clicking on the event list button on the main toolbar just takes me to the frame's event list, which isn't what I want.
Am I missing something?
There doesn't appear to be anything describing this in the help files. Clicking on the event list button on the main toolbar just takes me to the frame's event list, which isn't what I want.
Am I missing something?
You can't, not in the current version of MMF2. There are more serious things to be ironed out before things like this get fixed. :\
Working as fast as I can on Fusion 3
Just don't use behaviours - they're pointless.
Some people seem to be under the impression that events inside behaviours are somehow handled differently from other events, but that's simply not the case. The only advantage is that they save you having to copy & paste events when re-using objects (which takes all of about 3 seconds and 4 mouse clicks). The downsides are that you're forced to use the sucky event editor (not the event list editor), and you end up with code scattered all over the place (so it can be slower to edit code, and you're more likely to get bugs caused by events you'd forgotten about).
You'd be better off just putting all the code relating to the object into a single event group, and then copying that along with the object itself.
Aw, darn. I mainly just wanted to be able to look through the behaviors in Knytt Stories without having to double-click or hover over everything. -_-
I'll keep in mind those points about behaviors. It seems like there's some legitimate uses for them, though, like in Knytt Stories, where the frame code is massive and it'd be nice to be able to focus on smaller things separately from everything else, and widgets making it easier to share your code with other people.
I haven't worked with MMF too much yet, though.
Behaviours are sort of an all or nothing system. You either have to use them for everything, or use them for nothing. Mixing will make your code messy as hell. They're pretty useless overall too; ideally you should be able to write behaviours and then add them to objects in their properties instead of coding behaviours individually per object.
Good information. I was having difficulty in looking understanding to look at behaviors when trying to follow a tutorial recently, and sounds like I should not bother to use them moving forward
Posting Permissions
Reply With Quote