Yeah, would be nice.

Since the IDE is using the Fluent User Interface, maybe Scirra should try DotNetBar from DevComponents.

They have all the Office themes, a few cool custom themes, Visual Studio 2012 inspired themes, and they work on any Win version from XP onward. The themes can all be made easily customisable for the end-user out of the box, or can be tweaked by the developer to look they way they want.

They are very competitively priced, support is excellent, they release updates\bug fixes every Friday, and the forums are very lively if you need additional support.

Who knows you just may find the bugs causing all the C2 crashes in the process....

Hi Alcemon,

3 is the option to go with.

Check this blog from Tom, (Scirra Developer) Don't Waste Memory

It is good read and excellent information..

Thanks Ashley, all OK now!

Thanks for great support..... and an awesome product....

Ashley, thanks for looking into it.

Looking forward to next awesome release.

This fix is just in time for Windows8 Summer Competition too!

A little more info,

I know that third party plugins are not Scirra's problem, but I though it still might give some clues to go on...                   

On any of the panels except Permissions and Settings:

With both Scirra's and iunkin's:

Click any hyperlink - the Charms will close

Click anywhere on a blank area - the Charms will close

Click the Back button - the Charms will close

With other options available in iunkin's:

Click the Upgrade, or Reset buttons - The Charms will Close

Click either of the Audio sliders - The Charms Does Not close - but the the command is ignored

michael - can you post that info to the actual bug report thread? It could be quite useful, and it may be a while before I next get round to looking at it, and I might forget what you posted here otherwise.

Done.... :)

- occasional random crashes on exit: random issues are usually the most difficult to resolve, because if I can't make the problem happen every time, I can't start investigating it. I have once or twice luckily managed to catch the error in a debugger, and all I could determine was that the UI library we use crashed. We don't control that code, and we can't really report a random issue to the vendor because they also need to reproduce it every time. There's no immediately obvious route to start resolving this, so for the time being the issue remains open.

Ashley, this is what I had in mind when I started this thread, and I probably should have worded the topic title a little better (sorry!) - I don't mean to imply that you guys think bugs ARE ok, but more of what can we do to try to resolve this particular problem - because such are difficult to get to the bottom of.

Aside from the random crashes when exiting C2, there are others that occur when doing certain things - clicking below properties was one I can recall from other threads.

I have also had one several times that turns all the buttons on the ribbon to black squares and the event sheet just becomes a bunch of vertical lines. This one occurs when clicking the Preview Button, it is being caught (you get the error sound), but the error dialog must be behind the C2 window and thus you can't get to it because it always results in a complete program lockup, with the need to kill C2 using Task Manager. However you don't know this (except for the error sound) until you close the preview, the preview itself runs without any issues.

These particular problems all seam to point the finger at the UI - but as you say it is difficult to trace.

So perhaps you could open a thread with the sole purpose of trying to detail as much info as we can about these crashes. Maybe you and Tom have some ideas as to what we as a C2 community can do in order to pinpoint what is causing the issues....

I had similar problem on my Galaxy Tab 10.1. Not sure of the exact info but it was a JavaScript Error.

In my case I rebooted the modem, reset the address in C2 Preferences, restarted C2 in Administrator mode and all went OK after that...

Another thing I notice when playing around is if you open the charms and select Permissions, then the Back arrow, is does go back to the Settings page.

thehen,

OK, I tried simple project, removed the mouse object and exported it, added a couple hyper links to support page, but still exact same issue.

Oh man don't you hate that, just when you think you might be onto something...

That is using R126 by the way....

Ashley, here is the info I posted in other thread as requested:

....

I agree it is minor - to a degree.

It is annoying, yes, when the panel closes when clicking the back button.

But as stated, it is more than that, because it does stop the user accessing options presented to them. If they click any hyper links they don't work - it just closes the Charms and does nothing else, which is not good from a PR perspective - imagine an average end user clicking a link to send an email for support and it does nothing, what would they conclude from that?

I am thinking that it may not be the plugin that is at fault.

This morning I did a few install\uninstalls of C2 and found that up until r123 the Win8 Export works perfectly, including any hyper links - however with the release of R124 and all iterations after, the export no longer functions as intended.

This would seam to indicate that the plugin is not at fault here, something was introduced\changed in R124 that has broken both Scirra and iunkin's win8 objects.

There are a number of apps in the store built with C2, Mortar Melon, Battleship Islands, Ballo, Blast The Bricks, to name a few, that also illustrate that the plugins do work (the back button and any hyperlinks all function as expected), but these were built with versions prior to at least r119 I believe. This would seam to indicate that it is not Windows8 causing the issue.

So hopefully all this gives you a starting point to know where to look for a possible solution - start with what was added\changed in R124 that could be causing the issue....

thehen, will do.....

Just to let you guys know, the export works perfectly up to R123.

With R124 the Back button and any Hyper links fail to work as expected.