Hello, I am wondering if the buttons elements include different tones for the various possible button states: pressed, hover, or inactive states -- or are the button elements only in a single tone?

Thanks!

Just to chime it, it would be really nice to have some sort of table object in the game -- something that would facilitate the better display of information for game menus, player status, etc... They already support other html objects.

Well, I bought the laptop this spring -- it was an Asus with Intel imbedded ... (before I found C2) ... maybe an update will come soon -- I will just be much more conscious about my system limitation in development meantime. Thanks.

Ashley - After testing on multiple systems I can confirm this is only on my system.

I apologize for the trouble. My system is however up-to-date.

Why meeeee?

Ok, I'll try different system, but here is my shot of this capx in Firefox:

Problem Description

Setting a layer's transparency to 'no' in properties does not render properly in Firefox. This affects a large multitude of projects (in many cases making them unplayable in Firefox) , it also affects many of the sample capx included in C2.

Attach a Capx

I've just picked one of Scirra's own capx file -- the instance variables one.

Description of Capx

Instance variables example by Scirra (relies on layer transparency to present a clean background) .

Steps to Reproduce Bug

• Step 1 - Preview the project in Firefox
• Step 2 - Click a sprite three times. Observed Result Clicking your sprite logo makes the layer transparency problem evident. The example look bads and becomes confusing. Expected Result The layer to not be transparent. Affected Browsers
  • Chrome: (NO)
  • FireFox: (YES) v31.0
  • Internet Explorer: (NO)

Operating System and Service Pack

Win 8.1

Construct 2 Version ID

beta r175

The closest thing I've seen that might do what you want is the iscroll plugin. I would be interested in other options, too.

Yes, in my system compare opacity condition, I could have used IS > 0 rather than IS NOT <=0 ... But isn't that a difference without a distinction?

Nonetheless, yes a bug or dom problem .... ... and a frustrating one if you aren't aware. (for example, I work mainly with Firefox and didn't test other browsers until someone else pointed it out 'not working' ... because I was initially seeing layer transparency where there should have been none.) ... and I'm still curious about why the events don't get handled the same in IE (why the 'wait 0' action is necessary) ...

UPDATE: After submitting a bug report -- it turns out the Firefox issue I was experiencing was related to my specific setup (a fairly new Asus laptop with imbedded Intel graphics).

I need to learn more about the dom object. I also don't fully understand the issue with 6 and 7 being inverted -- the fade in/out should run at the same time - by design. One fades in while the other fades out... a large part of my learning process is figuring out best ways to do stuff in C2. I was using this to test layers with different background images in my game (not just colors) and just thought it might be useful enough to share.

The biggest problem I see is that Firefox does not honor the 'Transparency' property of the layer when set to 'No' (it is still transparent, except for around objects) ... and that with Transparency to yes, it is not 100% against object.

To see how this might fubar someones project, check out this guys game in Firefox.

I braved the creation of a tutorial to illustrate fading between layers and have discovered that each browser is different in how it handles the layers background colors with C2 r175.

You can test the project here and check the capx from my tut.

Here are the noted browser differences regarding background colors and transparency properties of C2 layers between browsers:

Firefox -- does not recognize the 'Transparent' property of layers cleanly. If 'Transparent' is No, the layer will still be transparent (except for areas around textbox objects) -- and if Transparency is 'Yes' when both a text box (on the transparent layer) and white (or black) background from separate layer is present the shades of white or black in the text box are slightly different -- not cleanly transparent.

Chrome -- perhaps the best -- seems to render as expected.

IE -- Opacity does not persist. Once the opacity of the layer being faded in reaches 100% it goes black. (EDIT - this was sort of fixed in IE by adding a wait 0 seconds to the end of the fade actions -- this prevented assigning the new layer variable too quickly in IE (but added a 'flash' at the end of the fade in IE), and it seems this should not have been necessary due to the order of my events.)

I'm not entirely sure how to address these differences -- file a bug report maybe? ... any suggestions are welcome... and also let this be a good reminder to cross-browser test your projects!

I tried your game in Firefox, many artifacts make it unplayable.

https://www.dropbox.com/s/v23etg2ii5qgfb6/Screenshot%202014-08-02%2014.06.07.png

DuckfaceNinja Oh cool ... I just knew I was missing something simple -- thanks!