Thanks Ashley, will do in the morning, when I am at my PC.

Hi, I think short sounds can cause errors like this. I had an issue way back where trying to import some audio files into C2 would cause the editor to hang, and it turned out to be the length of the files. I padded them out (added silence) so they were at least 00;00:001 in length and that solved the problem.

So maybe you could try padding the files, and see if it fixes your problem.

You can use Audacity to do that. It's free and awesome tool.

OK, was going to put this in the bugs forum, but it isn't really a bug with the C2 Engine, but just a glitch in the Styles for the Editor, hence no capx.

Just wanted to let Ashley know that Office 2013 styles do not retain the style for the tabs.

This is how the tabs appear when the style is loaded using View\Themes\Style options:

[attachment=1:1nmk7kjh][/attachment:1nmk7kjh]

This is how the tabs appear when you restart C2:

[attachment=0:1nmk7kjh][/attachment:1nmk7kjh]

So you have to reselect the style every time you start C2 so that the Tabs are consistent with the style.

And on a side note the status bar is always Blue, it would be nice if it would match the selected style. The Office 2013 Dark Grey style should be dark grey for example.

Just a minor thing but would love to see it fixed.

Sadly this is probably C2's only weak link - exporters - but as shown in this thread it is enough to break the chain!

As it is export for any desktop via node, is... well... broken...,

C2 itself is cutting edge and super cool to use, but the end result is too often broken, or production halted, by the reliance on third party exporters...

I get a little chuckle from the need to remove third party plugins form a capx when trying to sort a bug in C2 itself (and rightly so), but one of the biggest bugs we contend with are those we use to export our hard work with.

This node thing has been going on for ages now, and the blame is always placed on either chrome or node.

But is not the real problem C2's reliance on third party wrappers of whom the creators of such couldn't care less if it affects C2? Maybe they will get it fixed in the next few updates, but how long before it bugs out - again - in the following updates...

Other questions I contemplate are: Can they fix it? Do they actually know what to fix? Are they really trying to fix it?

If you look at Ashley's record, a major bug in C2 is fixed very quickly, sometimes overnight! But this can't be said for the node problem - which at the moment is a major bug...

Que Sera Sera....

Huh, always wondered how they get such realism in 3d games.

I could imagine it would fit some 2D games, the question is how do you make the assets workable (size\memory wise) how would that work with C2.

Hi michael I certainly like the style but being a little red/green colourblind the green looks very muted compared to the blue and orange. (Or maybe that's supposed to be red?)

hundredfold thanks for the feed-back. Yeah, actually I think you are right there.

Originally there was intended to be no colour, just grey tones for the collection. But when the pause controls are used over a game layout - for example displayed over a semi transparent black layer - I thought it would help to have subtle colours for the arrows of the Continue and Restart buttons (since both controls are similar in overall shape).

I'm thinking the orange arrow of the Restart control should be toned down a bit rather than making the Continue arrow brighter. Any thoughts....

The blue indicator used for some of the progress bars was just to demonstrate that you can use any colour for the bars.

Edit: Demo content removed, adding new screenshots soon.

Carbon UI Controls — Now for sale in the Scirra Store!

https://www.scirra.com/store/royalty-free-graphics/carbon-ui-controls-492

<h3>Cool and Stylish!</h3><div class="deshr"></div><p>Carbon UI Controls are designed to help you create a themed interface that looks cool, and adds a touch of polish to your games.</p><p>This collection contains 92 elements including 82 PNG images, 9 PSD files, and 1 example capx.</p><h3>The Product</h3><div class="deshr"></div><p>Fourty five carbon discs and symbols with pattern insets and semi-gloss overlays, along with four transition controls sporting transparent centres with semi-gloss overlays, combine to produce stylish buttons and pause screen controls for your projects.</p><p>Create themed dialogs, information panels, and home screens, with a choice of three TiledBackground and twenty 9Patch images.</p><p>Carry the carbon theme to sizable progress bars with a choice of two end caps and four bar covers, and you can of course change the carbon indicator bar to any colour of choice.</p><h3>Something Missing?</h3><div class="deshr"></div><p>If you like this pack, but it doesn't have a particular control you need for your project - please tell us - we just may be able to add it!</p><h3>Service</h3><div class="deshr"></div><p>The product ships with an example project (capx) to show how to set up the progress bars and 9Patch objects. The capx requires Construct 2 R184 free version or better.</p><p>We trust that you would be very happy with this product. If you have any queries or need further assistance please feel free to contact us.</p><h3>Check It Out</h3><div class="deshr"></div><p>To see these controls in a web application, please go here: cdasinnovations.com/demo/controls/index.html%3C/p%3E

Use this topic to leave comments, ask questions and talk about Carbon UI Controls

Yeah, same error with win8 VS 2012, and win8.1 VS 2013 exports

Just a Heads-Up on this OP.

I got a conflicting response about this from an on-line discussion with a MS rep, so I queried the Support Team and got this reply:

MS Rep says: The app has to be usable with keyboard and mouse input in any combination. (mouse or keyboard is acceptable) or the limitations have to be disclosed in the app description page.

So in other words mouse only is OK!

The problem was that the mouse wasn't working on their test machine as discussed in this thread.

Tylermon thanks for the reply.

Yeah sprite for cursor doesn't work in IE (win8 apps), hence using thehen cursor plugin. The problem is that it works on all our test machines as described in OP, so hoping for some light from Ashley as well.

It could even be MS not having updated drivers on test machine or something too, but how do tell them to update!

I think we will try updating it using the current version of C2, and hope it is a bug or something, and if that fails update without the plugin .Really would like to nail down exactly what it is before that though, but bit hard when it all works our end.

I've just fired of another email to MS to ask them to check if the problem exists their end in both Win8 and win8.1 releases of the app. But again it works our end on both counts there as well....

Hi fellow constructors.

Recently one of our apps on Windows Store FlapFleet Challenge has been reviewed by the Store Team, and they say the mouse cursor is not always present for navigation controls.

The problem is that in preview, when testing in VS, and the app itself when downloaded from the store do not have any problems our end.

So how do we fix that? Where do we start?

The app on the store was created with release R185 which had the UTF-8 problem when building the app (easy to get around), but aside from that all works fine our end as note above.

Ashley, I completely understand your capx requirement in bug reports now! Is it possible there could be other issues with that build (R185) that may only surface on certain systems.

DUTOIT, I understand from the various forum topics that you publish to Windows Store, have you had any issues like this\ any suggestions.

thehen, your cursor plugin is the only third-party plugin I use (thanks!). In all our tests it works as expected do you have any suggestions. I could take it out and see if it solves the issue. But again from our tests it all works fine.

Any suggestions\feed back would be much appreciated.

If you are building apps for Window Store, make sure the app has keyboard, mouse, and touch support!

Just had one of our apps reviewed by the Windows Store Team. And while the navigation supports mouse and touch, it has been pulled because it does not support keyboard.

Go figure...