tecbug TiAm

I had that same error message with NW.js. At line 440 in runtime.js I just commented out everything like this:

/*document.pointerLockElement =	document.pointerLockElement    	||
											 commenting out the above line makes this work as intended. Don't know why.
											 document["mozPointerLockElement"]	||
											 document["webkitPointerLockElement"];*/[/code:rfg10o93]
This also fixed the problem I had with "Mouse is currently locked" condition.

A couple of lines above in the runtime.js file it actually says "//the below isn't working. Commented out for now."
Was it supposed to be commented out and was just forgotten? 

Haven't noticed any issues so far after doing that.

There you have it.

Thanks for the quick explanation, Ashley!

Does anyone know if it's possible to modify an Sprite using css?

Thanks!

McKack

Not as far as I know.

I believe Ashley once said the text object can't be styled with CSS because it is rendered differently from control objects, and I assume that might be the case with sprites as well.

What do you want to do to the sprite, by the way?

Good thing we manually have control over what node-webkit version we use now, then

This is what a Steam rep has to say about it, btw (doesn't sound like they want to change anything on their side just yet):

[quote:cnqap37b]It looks like how they have things setup (maybe a giant canvas or webgl surface) does lead to consistent rendering, so that part actually may be working. Think the actual problem is that they are using the chrome multi-process model and the compositing and gpu rendering are each in a separate process from receiving input. So we inject the overlay hooks into all the processes, but we only find a 3d surface and try to run in the renderer or gpu process but some other process is doing input and we aren’t hooking it.

If they forced the single process model for their webkit/chrome stuff that might make things work without them having to heavily modify the chrome code.

Good news, everyone!: Screenshot on Steam

I'm incredibly excited about this in combination with the Greenworks plugin. Hopefully there's no side effects to using that argument.

Edit:

OK. Some basic testing done, not run into any problems so far. If anything, using the argument actually seems to increase performance slightly.

I went from reaching 30 fps ~8300 objects without it to 30 fps ~9600 objects with.

I think it's a separate issue entirely. Overlay works on Mac for me, but not in windows. I've reported to rogerwang here: https://github.com/rogerwang/node-webkit/issues/2560 if you want to add any comments there..

Thanks, I'll keep an eye on that issue post.

What's interesting is, I just discovered Game Dev Tycoon has working overlay on Windows, so the good news is it is possible somehow with node-webkit. Would love to hear from greenheartgames how they did it and if it translates into something that may be applicable for us as well.

Amazing news! Does this help with missing Steam overlay or is that a separate node-webkit issue?

Edit:

For anyone else OCD about the plugin icons in C2, here's a temporary icon for you until it gets an official one.

Download here

—

istavang

Sorry about all this. It would appear solidfiles have turned to dubious methods of earning money. The big green download button leads to some shady downloader/installer while the tiny link underneath it is the clean file as far as I can tell. Either way, I've replaced the links with safe ones.

I'll never be using solidfiles again!

delgado I wrote it in Sublime Text 3. In other words, any text editor you prefer

Cipriux Great!

delgado

You'll wanna use the text object, it has support for web fonts (Not recommended/supported for mobile if I recall correctly, though)

Another option is to create a spritefont using that font.

https://www.scirra.com/tutorials/236/using-web-fonts-in-the-text-object

https://www.scirra.com/manual/166/sprite-font

Handy CSS documentation / tutorials can be found here:

http://www.w3schools.com/css/DEFAULT.asp

Yes, that can easily be done in the index.html for deployment. Hopefully there'll be more settings and control over the index.html appearance in future versions of Construct 2.

This plugin is mostly just intended for realtime usage or testing in preview.

In any case, for future reference if anyone wonders, using the plugin, here's some examples of how it could be done:

For just the layout.

Set the layer(s) in your layout to transparent and add the following to the stylesheet.

#c2canvas {
	/* Support for most browsers */
	background-image: -ms-linear-gradient(top, #000000 0%, #EF1A7E 100%);
	background-image: -moz-linear-gradient(top, #000000 0%, #EF1A7E 100%);
	background-image: -o-linear-gradient(top, #000000 0%, #EF1A7E 100%);
	background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0, #000000), color-stop(1, #EF1A7E));
	background-image: -webkit-linear-gradient(top, #000000 0%, #EF1A7E 100%);
	background-image: linear-gradient(to bottom, #000000 0%, #EF1A7E 100%);
}[/code:3tumn0kj]
[b]For the entire page.[/b]
Add the following to the stylesheet (notice the "body" instead of "#c2canvas").
[code:3tumn0kj]body {
	/* Support for most browsers */
	background-image: -ms-linear-gradient(top, #000000 0%, #EF1A7E 100%);
	background-image: -moz-linear-gradient(top, #000000 0%, #EF1A7E 100%);
	background-image: -o-linear-gradient(top, #000000 0%, #EF1A7E 100%);
	background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0, #000000), color-stop(1, #EF1A7E));
	background-image: -webkit-linear-gradient(top, #000000 0%, #EF1A7E 100%);
	background-image: linear-gradient(to bottom, #000000 0%, #EF1A7E 100%);
}[/code:3tumn0kj]

Sorry for the late reply, but glad to hear you figured it out.

+1

Condition checking family instance variable when no objects of family are present in layout invokes a crash.

Condition checking instance variable when no [non-family] objects are present in layout does not invoke a crash.