I thought it was a perfectly valid question, especially since there ARE known issues with glbasic and IOS4. And I tend to find this community has a very short attention span when it comes to existing threads and issues, so it made sense to me to ask it in a new thread.

Any other questions we shouldn't ask? I wouldn't want to upset anyone...

Oh ok. So the issue that ALL GLBasic apps crash on exit under iOS4 before executing GLB_ON_QUIT on a multitasking compatible device is solved, is it? Because no one bothered to mention it in the bug thread. The last comment from a dev is August 26th saying "OK, I think I have a slight idea where the problem is now. I'll try to fix that soon. Next week at the latest.". And then nothing at all.

Which exactly illustrates makes my point about existing threads and issues, really.

If it is fixed, would have been kinda handy to know, since I've been waiting to update my broken apps since the launch of iOS4, while watching the bad reviews roll in and sales plummet.

Rather than waiting to be told, you could maybe test it yourself once an update is posted, and then perhaps inform others who are awaiting and answer. Just a thought

The GLBasic community is one of the best communities I have had the pleasure of being a member of. i have been in lots of development forums that are very sercretive and dont wish to share anything,this community is not like that and therefore deserve a little more credit

That thread relates to problems with the introduction of GLB_ON_PAUSE and GLB_ON_RESUME, as far as I can tell? Not really sure what the 'AUTOPAUSE' feature refers to. Nothing to do with the issue I posted about at length. If it is, it was way too subtle for me.

Kinda illustrates my point yet again. I've stated time and again that the introduction of these two functions DID NOT solve the original crash issue. They are two seperate issues: (a) fixing a bug that causes a crash on all multitasking devices, and (b) Adding capability to support multitasking. If (a) WAS fixed, surely a ONE WORD post saying 'solved' in my bug report thread would have been the logical thing to do?

Rather than waiting to be told, you could maybe test it yourself once an update is posted, and then perhaps inform others who are awaiting and answer. Just a thought

Except I'm getting less and less inclined to use it for serious development, my problem with updating GLBasic is that it can often cause more problems than it fixes. So I'm extremely careful about whether I get the latest updates or not... especially when they come with an admission of no testing and Gernots own advice is to only use if you have to. "I had no real time to test all platforms, so please only update if you really experienced a bug. If others confirm it's OK, it might be safe. Sorry - but I'm really busy these days."

If I'd been aware of it being fixed, I'd have tested it and posted my findings. If you've ever read my bug reports, which you evidently haven't, you certainly can't accuse me of NOT thoroughly testing and writing up my findings. Thing is, no matter how detailed my writeup of symptoms or issues, it's often painfully obvious from any responses that they're not even being read properly, so it feels like I'm wasting my time. Also, who are these "others who are awaiting and answer" that I have an obligation to? I wish I felt that ANYONE else here actually cared about any of the issues that are important to me. These people ought to perhaps speak up so it doesn't look like the issue is just affecting one person. Maybe it'll get looked into faster.

I'll refrain from commenting on the other part of your quote, as much as I'd like to state a few home truths.

multitasking is a feature of ios4 and crashes because no device for testing. no device -> no 100% bug fix. understand?

I think I understand, thank you, despite your somewhat mixed messages. You're saying that I can't realistically expect my apps not to crash on iOS4 and that Steve Jobs was completely correct about relying on 3rd party development platforms, yes?

OK, I really was short on time the last few weeks. But I got my IP4 and I will fix the rest of the mutitasking ssues - if there are any.If it crashes with the current update, I bet you are doing some graphics while you oughta pause, which is by design prohibited. A shame it crashes, though.