Printable View
Was a solution ever found for deleting objects that MMF wouldn't let you delete (even though you'd eradicated all trace of them in the Event Editor and killed them all off in the Frame Editor)?
I would really rather avoid having to piece my frames together from scratch. It seems a bit unnecessary just to delete active objects.
Have you tried copying and pasting the actual frame?
Delete all references as you said, save a new .MFA, delete all the events in the event editor, then copy/paste the entire frame, and into it paste the events from the old MFA.
Thanks I'll give it a shot! - Just to be clear:
I create a new app, paste the frame across, delete the events in the new frame then paste the events back in from the old one?
I'll have a crack at it now!
EDIT: Sadly, it wouldn't bite - just refused to save, crashed or tried to lock up my PC.
No no, he said to copy the entire frame (only the objects in it, not from the storyboard editor) into the new MFA. Then copy the events over.
Err actually I meant the other way, but try both! >.>
I had one of these happen a while back, and copy/pasting everything cleared it
Sorry, now I understand. This is what I was trying to avoid...
Unless, is there a quick way to copy the objects that are in the Frame Editor List but not in the main Frame Editor Window?
It's just that 90% of objects are created by the Event Editor and aren't in the Frame at the start.
Although I suppose I could dump all the desired objects in the frame and take those across and delete them again afterwards.
Copying the events will copy the objects being created.
Are you positive? I've never been able to get MMF to do that.
If you paste your events, where objects are created but not sitting in the Frame Editor already, I just end up with a load of red, broken apple shortcuts/placeholders.
I always have when I've tried in the past too. Is that not normal behaviour for the program?
I copied the objects in the frame across into a new frame (even in the same application) and then I copied the events across into the new frame as well.
I appreciate your patience with this.
It works for me, every time. :\
Crash86: If you end up with broken apples, place the objects in the frame and disable the "create at start" runtime property. It's more convenient to have them in the frame anyway.
Also, a nice hint is to fix undeletable object problems last. In Saira I got them around 3-4 times, and it was anoying to deal with all those objects in all those layers only to realize it would happen again later.
I think that's probably right - I'll just work around them for the time being and see how many I wind up with at the end.
Good to know it's not just a problem exclusively with my file.
Thanks for your help guys.
Impossible the problem of the undeletable object (a.k.a.:Ghost object) be corrected by updating MMF2?
Sorry, I'm on the latest version and I still get- and can't delete those objects.
...though I can understand why bugs like this can emerge easier when the object's existence rely on if they're in a frame and/or creation event. Personally, I think the existence of an object shouldn't rely on if an instance of it exists on the frame or anywhere else. I think it'd be great if there were simply a single object list, not bound to the frames, with self-contained objects sorted into folders and sub-folders that can be dropped onto any frame. MMF3 perhaps :)