BAD OBJECTS!!!!

[Werbad]

I've only had Bad Object references when I copy code with Extensions not used in the frame...

[Nifflas]

Should it? Normally i get a Counter Icon with the shortcut arrow when i paste an Event with a Counter from one app to another. But from time to time i get this baddie icon instead as shown here.

Oh, right, that's what actually is supposed to happen, I forgot! Sorry!

I wish I remembered more from the only moment when this happened to me. Luckily for me, I always keep tons of backups, but even starting over from an two-hour old backup can be a bit of a pain.

[Francois]

There is a difference between "good" bad objects and "bad" bad objects.
The good ones are the ones when you copy code with one extension not present in the frame. They disappear when you drop the missing extension with the correct name.
The bad one do not disappear, and when they are there, the application goes berzerk. These ar ethe ones I want to get rid of.

[Crash86]

What irritates me are the objects that don't perform as they ought to and cause the program to go corrupt / crash but aren't flagged up as bad objects in MMF2.

I think the solution is a feature to "test" an MMF2 application's objects for damage / corruption as Microsoft Access has an option to compact its databases.

The statement at the start of this thread that bad objects and 'ghost objects' that are lost track-of in a way by MMF2 are rare is an outright fabrication. The problem has dogged my project for years.

I do however agree that using the Event Editor to create objects and deleting the originals from the frame editor causes havok in MMF2 even if (in my view) it absolutely shouldn't.

Saying that I shouldn't make my application this way is ridiculous. It's perfectly valid only that MMF2 has a serious bug relating to it.

[00J]

[color:#FF0000]Francois[/color], I notice in Tiles' picture there are Edit Boxes, I had a bad object once before and I had Edit boxes in my app, and I think I had objects connected to the Edit boxes somehow.

Could the Edit box have something missing or be the cause?

I've only gotten this problem once a few years ago, and it had to do with the Edit Box Object, inside a behavior linking to another object.

I do however agree that using the Event Editor to create objects and deleting the originals from the frame editor causes havok in MMF2 even if (in my view) it absolutely shouldn't.

Saying that I shouldn't make my application this way is ridiculous. It's perfectly valid only that MMF2 has a serious bug relating to it.

Absolutely. You are right about this. You can't say this issue hasn't been addressed, it's dogged MMF for years... [laugh]

It's the king of all bugs, and just when you think you've got it knocked out, it's back again...

The trick is to narrow down the problem to a few possibilities.
Hopefully it isn't spread throughout MMF.

I can say though that I don't get this Bug at all anymore, I think it's due to my coding method I really keep a straight forward design, just me.

[Francois]

The bad objects are definitively linked to extension objects. Not specifically the List Object.
If someone can make me a way to make MMF go Hvok by removing the objects, please send it to me!