Bug - Strings Cannot be Completely Destroyed.

[Docilemouse]

As was just discussed in a post I very recently made, Strings can't be entirely destroyed. I thought it was just a mistake I was making, but apparently it might be an actual bug.

When you try to "destroy" a string, all it really does is delete the text inside it. The debugger still shows that the object exists, and it seems that the string still taxes the computer just as much as when it is visible.

[netninja]

I can verify this. I posted about it in March of this year:

http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Main=18848&Number=1335 37#Post133537

Please fix this bug.

[Francois]

It is not a bug. It is by design, from K&P in 1994. If corrected it would cause many programs not to work.

[Pkeod]

Cause them to work in what way? Is the fix going to be a part of MMF3 then? :V

[Crash86]

Oh right - so you can destroy them in the Frame editor but not from an event, while the program's running...

Well that's not so bad.

[RickyRombo]

I had a feeling it was like that for a reason

It wouldn't be like Clickteam to not fix it otherwise

[Nifflas]

There are some design mistakes that still exist because of historical reasons, which is why I hope that one day MMF (3?) can get a fresh start without having to support all the previous versions.

[Crash86]

Why don't you introduce a String Mk.II object and put it in subsequent updates?

[Nifflas]

We need an extension developer to create a raster variable-font-width alpha channel text displayer anyway, so we're probably better off paying someone who wants to do that. I however don't think we should "fix" things by add stuff to the top of what we already have, as an alternative to starting fresh. That's where software bloat comes from.

[Jax]

However, wasn't MMF1.5 compatibility a big issue for users when MMF2 came out?

I do wonder what it has been designed like this though. I'm not really complaining but I hate not understanding things =D