Thanks for the reply GeometriX, but my main issue, and I believe rekjl's original one as well, was not about the code logic, but rather about the actual sensor value readings

And probably most people indeed use the values for C2 games like you described, but this mechanism doesn't work for "absolute" orientation, because the numbers are not "proportional"

For example you can try yourself, if you lift the left side of your device to read Gamma 45, it's actually just around 30 degrees rotation (and then catch up fine at Gamma 90 / 90 degrees)

Like I mentioned before, this looks like ease-in ease-out, and I'm starting to wonder if C2 is applying that on purpose for more precision with the kind of gameplay mechanism you described

But then it breaks the option to make a simple compass, and I still invite anyone to make a working one using the Alpha value...

Hey GeometriX, we're having a hard time understanding the orientation readouts over here

Can you tell me if your example is meant to work as a compass, or at least did it use to work as a compass in a previous C2 version at that time?

In my case it's turning "faster" at some point than the tablet, and I'm still trying to figure out whether to report it as a bug or not

Yeah I'd be keen to use it for 3-axis application, especially since Q3D went live

I might consider posting in the bug section if no one has an explanation

Maybe Ashley can shine some light on this?

Hey I'm experimenting with the orientation sensors, and having the same results

For example the Alpha seems to be okay at 0/180/360, but in between changes in some kind of non-linear ease-in ease-out way

Not sure about the Beta and Gamma... are we expected to do math related to euler angles & gimbal?

The manual says "Alpha is the compass direction in degrees", so I would expect a linear change while rotating my device (nexus 7)

Are we missing something, or can other people try this too and explain the results?

Feel free to post a capx as well if anyone manages to do a simple 2d compass for example that works

Hey I'm considering checking out this plug

Is it possible to apply C2 webgl 2d effects on the 3d rendered layer?

With the "inside" mode?

like a glow for example

Sweet, thanks for the tip! it works indeed at export (but not in preview)

I wouldn't say it's "very easy" to handle or switch though, maybe we could have a new Nodewebkit action inside C2 for that,

Or if it's meant to work only after package, maybe a [frameless] box to tick in NW export option?

Sorry to resurrect this thread, but I've been playing much with NW too lately,

And after having a look at the docs, I agree that something like a frameless window would be a really neat thing to have indeed

It would add a bunch of design possibilities for both widget-like apps or games

https://github.com/zcbenz/nw-sample-apps/tree/master/frameless-window

Nice :]

Thanks for the fast update!

Problem Description

Can't read file sizes with Node Webkit

Attach a Capx

https://drive.google.com/file/d/0B6wXdu ... HFhSDN3cFk

Description of Capx

Let the user pick a file, then display the file sixe in the text field

Steps to Reproduce Bug

• Set a file path for Node Webkit
• Use NodeWebkit.FileSize to retrieve the size

Observed Result

[quote:cqzol748]Uncaught node.js Error

TypeError: Cannot read property 'apply' of undefined

at ExpNode.eval_object_behavior_exp (http://localhost:50000/expressions.js:337:28)

at Parameter.get_exp (http://localhost:50000/eveng.js:2049:19)

at Action.run_object (http://localhost:50000/eveng.js:1808:32)

at EventBlock.run_actions_and_subevents (http://localhost:50000/eveng.js:929:38)

at EventBlock.run (http://localhost:50000/eveng.js:886:9)

at Runtime.executeSingleTrigger (http://localhost:50000/preview.js:4118:10)

at Runtime.triggerOnSheetForTypeName (http://localhost:50000/preview.js:4037:16)

at Runtime.triggerOnSheet (http://localhost:50000/preview.js:3969:13)

at Runtime.trigger (http://localhost:50000/preview.js:3946:12)

at HTMLInputElement.<anonymous> (http://localhost:50000/NodeWebkit_plugin.js:86:18)

Expected Result

File size retrieved

Affected Browsers

• Chrome: unrelated
• FireFox: unrelated
• Internet Explorer: unrelated
• Node Webkit: YES

Operating System and Service Pack

win 8 64bit

Construct 2 Version ID

174

Node Webkit v0.10.0

Hi, has anyone been using NodeWebkit's FileSize expression recently?

I guess it's not widely used, unless you're not making a game (like me)

Couldn't find anything in the forums though, here is what I tried so far, did I miss something?

Not posting as a bug yet, but here is the error I get:

[quote:pa4kjvug]Uncaught node.js Error

TypeError: Cannot read property 'apply' of undefined

at ExpNode.eval_object_behavior_exp (http://localhost:50000/expressions.js:337:28)

at Parameter.get_exp (http://localhost:50000/eveng.js:2049:19)

at Action.run_object (http://localhost:50000/eveng.js:1808:32)

at EventBlock.run_actions_and_subevents (http://localhost:50000/eveng.js:929:38)

at EventBlock.run (http://localhost:50000/eveng.js:886:9)

at Runtime.executeSingleTrigger (http://localhost:50000/preview.js:4118:10)

at Runtime.triggerOnSheetForTypeName (http://localhost:50000/preview.js:4037:16)

at Runtime.triggerOnSheet (http://localhost:50000/preview.js:3969:13)

at Runtime.trigger (http://localhost:50000/preview.js:3946:12)

at HTMLInputElement.<anonymous> (http://localhost:50000/NodeWebkit_plugin.js:86:18)

Yup, like he says

Sweet :]

I replaced my nodewebkit with the last version and it works indeed now

Thanks mate