Hello World,

So I plan to go through the update process again(man I hate these moments...) and I was just wondering, do I need nwjs(previously known as node-webkit) if I don't plan to make .exes for windows?

More specifically does C2 run 100% correct, with everything(browser testing included, etc.) without nwjs? Or does nwjs have some other functions/ways in which it supports C2 besides exporting exe?

Thank you.

P.S. Ashley if you are around can you pretty please tell me if another stable release is right around the corner before I do this? Cause if there's a chance that a new stable will pop-up in a day or two I'd rather wait untill then.

None taken j0schi .

and there are much more important bugs without workarround

While I agree with that in theory, the problem is that statement is completely subjective. For me this is the most important bug right now because this is the problem I am dealing with right now. Someone else has another problem and of course that is gonna be the most important bug for him... etc.

As to how hard/easy it is to fix I have no idea, might be super hard/might be super easy, Ashley can figure that part out and decide where to put it on the priority list.

Anyway untill then, thanks to Magistross 's brilliant idea, I now have a real workaround set sliderbar css style "opacity" to "0"

Check rexrainbow 's csv to array and csv to dictionary plugins. You should be able to do what you want with those I think.

Not sure about the best simple way of doing this, but here's how I would approach it:

1. I would edit the animation of the "phone" object and add another image point and place that point in the upper-left corner of the "phones" "screen".

2. Then I would take the other sprites, I make them initially invisible and set their origin points to 0, 0.

3. Then I would make events if sprite position(x, y) is equal to the position(x,y) of the "phones" image point, then set sprite x visible.

If it's not equal then set it back to invisible. And do that for both sprites, or if you have more sprites, create a family put them in it, and then do that event for the family.

YEEEEEEEEEEEEEEEEEEEESSSSSSSSSSSSSS!!!!! See guys( LittleStain nimos100 ) that's what I'm talking about!!!!

It worked, it's simple, it's easy and now I can get on with my life!

Thank you so so very very much Magistross , awesome idea!!!!

I know that j0schi but:

1. Why should I have to do that?

2. Just cause there is an alternative doesn't mean you shouldn't report bugs.

3. What do you think is easier for my music/sound volume: a "do it yourself" event sheet with half a page full of events with complicated formulas/actions in them in order to make my own slider; or using the sliderbar(beeing able to hide it so I can cover it with some nice sprites that fit the theme/look of my game) and then having one event on sliderbar changed action set volume to sliderbar value?

Sigh... Well then I guess I have to eighter wait for Ashley to fix the invisible bug(I've submited a bug report) or use one of those methods and make it myself.

I was sooo hoping there was a quick, easy and simple method of hiding the sliderbar, I had no idea it was a Dom element or that those elements where drawn above the canvas....

Anyway, thank you guys.

Problem Description

____ The sliderbar stops working if you set it to invisible.____

Attach a Capx

____ https://www.dropbox.com/s/35vcjhkg5zrru ... g.rar?dl=0 ____

Description of Capx

____ The capx puts a sprite "above" the sliderbar and has 2 events to make it follow the movement of the slider. The whole idea is to cover up that ugly sliderbar with your own sprites. But of course we know you can't actually do that because(as I recently learned) the sliderbar is a Dom element, and those elements float above the canvas. So the next logical step is to set the sliderbar property "Initial visibility" to invisible. If you do that the sliderbar doesn't work anymore. ____

Steps to Reproduce Bug

Step 1 [Run the capx and see that the sprite follows the slider, and everything works fine.] Step 2 [Set the sliderbar object property "Initial visibility" to invisible.] Step 3 [Run the capx again.]

Observed Result

_____The slider no longer moves/works if set to invisible. ____

Expected Result

____The sliderbar should keep working regardless if it's set to invisible or not. ____

Affected Browsers

[YES] Chrome: (YES/NO) [YES] FireFox: (YES/NO) [YES] Internet Explorer: (YES/NO)

Operating System and Service Pack

____ Windows 7 Ultimate 64 bit(6.1, Build 7601) ____

Construct 2 Version ID

____ Release 200 (64-bit) ____

I've said this before and I'll say it again.

Olso(from everything I've learned so far, correct me if I am wrong guys) the most important thing isn't how powerful your hardware is, but how you design your game.

If you design your game poorly(too many effects, too big resolutions on your sprites, poor code/too many every tick events, etc.) then theoretically you can bring any pc/tablet/phone/etc. to a crawl, no matter how powerful it is, even with a 2D engine...

Replacing the every tick events in this capx is hardly an effort..

And how would you modify that capx to not use every tick for example?

If you were to set the slider-bar invisible and use sprites to influence it, it would be much the same as the link I gave except for the extra slider-bar object..

Yeah, expect for the fact that the stupid sliderbar stops working if you set it to invisible.... I'm not sure if that's a bug, or if it's supposed to be that way, but it just doesn't work while invisible....

No, it wouldn't zenox98 . Because, like I said above, it works perfectly well in the browser, so a capx would be useless. What I am talking about is how it works once it's exported, wrapped and installed on an actual device...

I already had that capx downloded LittleStain , and I already had 2 problems with it:

a) It uses an every tick event, and I would like to keep the use of every tick to an absolute minimum.

b) It has a blank even, probably a mistake or oversight from it's creator, so I wouldn't know what to put in that event if I tried to replicate it.

Here's what I mean by blank event:

And while it is less complicated then the other example capx that I was referring to, it's still way more complex then using the sliderbar(if I could hide it) and then just basically having 1 event on sliderbar changed action set volume to sliderbar value....