[UPDATED: 05.09.2017] The Big NW.js Roundup - Tips & Tricks

Discussion and feedback on Construct 2

Post » Fri Oct 13, 2017 6:41 am

I did the tests with nwjs 0.25 both Win7 and 10, resizable and non-resizable.

    1. I got the same result.

    2. Win10 and non-resizable gave me "652x370".
    The rests are the same.

    3. I got the same result.

    2+3. Win10 and non-resizable gave me "652x370" again.
    The rests are the same.

The same result refers to the post I did above.
So it affects somewhat win10 to set window size through the plugin.

To be clear, I did "System:set canvas size to NWjs.WindowWidth x NWjs.WindowHeight" as the manual setting.
If that's not what you meant, please let me know.
B
13
S
6
Posts: 10
Reputation: 1,010

Post » Fri Oct 13, 2017 1:19 pm

taker7 wrote:I did the tests with nwjs 0.25 both Win7 and 10, resizable and non-resizable.

...

The same result refers to the post I did above.
So it affects somewhat win10 to set window size through the plugin.

To be clear, I did "System:set canvas size to NWjs.WindowWidth x NWjs.WindowHeight" as the manual setting.
If that's not what you meant, please let me know.

Hmm... that's bad. I have no Win10 machine but I can reproduce it on my Win7 and 8.1 machines so the OS doesn't seem to be at fault here.
Could you please upload the latest projectfile (capx) so that I can look into possible workarounds on my end.

I will give you an update in here if I find something that works. For now we gotta hope that the Chromium Dev's do their work.
ImageImageImage
B
63
S
23
G
78
Posts: 661
Reputation: 44,935

Post » Sat Oct 14, 2017 6:06 am

Sure, here is the capx.

https://drive.google.com/file/d/0B1SDO1 ... sp=sharing

The posts about the bug here can be a reference point for people struggling from it.
I hope either we find a workaround or the chrominum team fixes the bug.
B
13
S
6
Posts: 10
Reputation: 1,010

Post » Sat Oct 14, 2017 6:46 am

I think it's been a problem for a while. https://github.com/nwjs/nw.js/issues/1712
A big fan of JavaScript.
B
74
S
20
G
71
Posts: 2,228
Reputation: 44,888

Post » Mon Oct 16, 2017 3:08 pm

taker7 wrote:Sure, here is the capx.

https://drive.google.com/file/d/0B1SDO1 ... sp=sharing

The posts about the bug here can be a reference point for people struggling from it.
I hope either we find a workaround or the chrominum team fixes the bug.
Colludium wrote:I think it's been a problem for a while. https://github.com/nwjs/nw.js/issues/1712

Thanks for the file and further information about this. Will look into possible workarounds soon™.

I'm currently waiting for the next stable NW.js release, which usually comes out a day or two after the stable Chromium update.
Judging by their calender it will be released on the 17th, will update this topic with a couple of other minor workarounds soon.
ImageImageImage
B
63
S
23
G
78
Posts: 661
Reputation: 44,935

Post » Thu Oct 19, 2017 10:58 am

@taker7 I cannot reproduce this in the latest version of NW.js on my end (while using no workarounds at all).
Could you please check it out yourself and confirm if it's indeed fixed or not?

My two other workarounds for the mousepointer issue and instancing issue are both no longer working, meaning that I won't update this topic anytime soon.
ImageImageImage
B
63
S
23
G
78
Posts: 661
Reputation: 44,935

Previous

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 19 guests