[UPDATED: 11.12.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
15
S
8
Posts: 13
Reputation: 1,316

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
74
S
26
G
78
Posts: 702
Reputation: 45,631

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
15
S
8
Posts: 13
Reputation: 1,316

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. Image Image
B
76
S
20
G
81
Posts: 2,347
Reputation: 50,188

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
74
S
26
G
78
Posts: 702
Reputation: 45,631

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
74
S
26
G
78
Posts: 702
Reputation: 45,631

Post » Sat Oct 21, 2017 5:52 am

@TheRealDannyyy
Unfortunately, I still got the same result.

Just in case, I uninstalled old nw.js and then installed the new one.
I made a new fresh project and tested what you wrote before with win7 and 10.
Here are the exported file and Capx. I used r247 and nwjs26. The resizable option is unchecked.


I'm curious there are other people cannot reproduce the issue or not.
If that's the case, there might be something wrong on my end.
B
15
S
8
Posts: 13
Reputation: 1,316

Post » Sat Oct 28, 2017 6:10 pm

taker7 wrote:@TheRealDannyyy
Unfortunately, I still got the same result.

Just in case, I uninstalled old nw.js and then installed the new one.
I made a new fresh project and tested what you wrote before with win7 and 10.
Here are the exported file and Capx. I used r247 and nwjs26. The resizable option is unchecked.


I'm curious there are other people cannot reproduce the issue or not.
If that's the case, there might be something wrong on my end.

I can reproduce it using your example, that's the strange thing about this. When I open the example and export it myself, I cannot reproduce it at all so something must be wrong with your version of NW.js I assume. (Using NW.js v0.26.0, Windows 7 64bit on a Desktop PC.)

Can you please completely remove NW.js manually and install the most recent version from Scirra's page?
Maybe also remove the manifest files and replace them with "reset" ones found in the How To: Add Chromium-Args & JS-Flags section. (Backup your manifest files just in case.)
ImageImageImage
B
74
S
26
G
78
Posts: 702
Reputation: 45,631

Post » Wed Nov 08, 2017 7:16 am

@TheRealDannyyy
Sorry for the late reply, I finally got around to do what you suggested: uninstal NW.js and "reset" the manifest files.
I also uninstalled and reinstalled C2. Just in case I deleted 3rd party plugins and behaviors too.
To be clear, I tested with r247, NW.js 0.26 downloaded from Scirra's page and win7/10 64bit on desktop PC.

I still got the same result. I did that with both win7 and 10 again.

Did "manually uninstall NW.js" mean:

    Control Panel, Programs, Programs and Features, select NW.js and click uninstall?
That's what I did and if that's not what you meant, could you tell me how to manually uninstall NW.js?

Also I was wondering if you could upload your capx and exported file like I did last time so that
I could try them out. Sorry for keeping bothering you.

If anybody tries the test and share what you get here, I'd appreciate it.
B
15
S
8
Posts: 13
Reputation: 1,316

Post » Tue Nov 21, 2017 11:53 pm

taker7 wrote:@TheRealDannyyy
Sorry for the late reply, I finally got around to do what you suggested: uninstal NW.js and "reset" the manifest files.
I also uninstalled and reinstalled C2. Just in case I deleted 3rd party plugins and behaviors too.
To be clear, I tested with r247, NW.js 0.26 downloaded from Scirra's page and win7/10 64bit on desktop PC....

Sorry for the late reply as well. First things first, no need to re-install NW.js or do something like that, it's not necesarry.
I know I'm late and the most stuff is already known on Github but below you can check out my findings and experiment around yourself.

My Observation:
Using the information from Github it's clear that Chromium has an issue with non-resizable windows (+high DPI display). From my tests, this issue is not only affecting high DPI displays but also regular displays. Feel free to test it out on your end and post your results.

My Tests:
Files & Requirements:

Issue #1 - Window Size Issue (Exported Version):
  1. Set "Use high-DPI display" to YES/NO
  2. Export your project (Window Frame: YES | Resizable Window: NO | Kiosk Mode: NO)
  3. Notice incorrect window size regardless of the DPI setting

Issue #2 - Not Resizable Action Is Broken (?):
  1. Preview the project (in-editor or exported, doesn't matter)
  2. Enable advanced settings
  3. Click on "Resizable Window OFF"
  4. Try to resize the window (should be possible even though it's disabled)
  5. Click on "Resizable Window OFF" and notice that you can resize it again

Last Words:
I've included a possible workaround that you can try out but it's not perfect and "hacky", that's why the event-structure might look a bit weird at first.
I might post a reply in the Github thread with all the new information soon but for now we have to wait for the Chromium Dev's to do their work.
ImageImageImage
B
74
S
26
G
78
Posts: 702
Reputation: 45,631

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 5 guests