Dynamic binary eval.

[kilgaloon]

Hello everyone,

I just noticed that when i try to load binary files dynamicaly, for example, using for loop and looping through some array for example:

var arr = ["home","front"];

for(i=0;i<arr.length;i++) {
require('nw.gui').Window.get().evalNWBin(null, process.cwd() + '/' + arr[i] + '.bin');
}

home.bin get executed twice. It never get to front.bin.

Anyway no mather how much arr is long, first element will be evaled for arr.length times.

OS: Debian Jessie x64
NW: 0.14.6

[ghostoy]

I will look into this issue.

Strahinja [email protected]于2016年7月30日周六 23:15写道：

Hello everyone,

I just noticed that when i try to load binary files dynamicaly, for
example, using for loop and looping through some array for example:

var arr = ["home","front"];

for(i=0;i<arr.length;i++) {
require('nw.gui').Window.get().evalNWBin(null, process.cwd() + '/' +
arr[i] + '.bin');
}

home.bin get executed twice. It never get to front.bin.

Anyway no mather how much arr is long, first element will be evaled for
arr.length times.

OS: Debian Jessie x64
NW: 0.14.6

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#5168, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAczeAez-n4rVJ0bMW8GczXrpNq5jmsTks5qa2p3gaJpZM4JY06U
.

[ghostoy]

@kilgaloon I cannot reproduce this issue. Here is my test case: https://gist.github.com/ghostoy/183649c64060b088a610ebc142fae3d2

I got foo and bar both in the console.

[kilgaloon]

Can you put for loop in another bin, then try.

[ghostoy]

@kilgaloon What do you mean by "another bin"? A third one?

[kilgaloon]

@ghostoy Yes, put for loop in third bin, lets say main.bin and try it like that

[kilgaloon]

For me it actually doesn't mather where im doing for loop. im using following snippet of code:

   results = ["main","front","admin"];     
   for(i=0;i<=results.length;i++) {
      nw.Window.get().evalNWBin(null, process.cwd() + "/plugins/" + results[i] + "/" + results[i] + ".bin");
    }

every of this bins have corresponding log depending of their name console.log('main loaded.') etc.
So, what ever i do i get 3 main loaded, if i put front to be first element i will get 3 front loaded. This is getting weird since you guys can't reproduce this. But im getting same with jQuery.each function or with classic for loop.

[ghostoy]

@kilgaloon Could you upload your entire test app as attachment?

[kilgaloon]

I'll contact you on gitter

[ghostoy]

@kilgaloon It's quite late for me. Please send attachment to Github and I'll check it tomorrow.

[kilgaloon]

Project is kinda big, can you give me some where i can privately share it with you?

[semmel]

I can confirm that multiple evalNWBin commands always execute just the .bin which was first specified. It has nothing to do whether the bins have a relative or absolute path.
System: OS X, nwjs 0.16.0 (SDK)
To demo I took @ghostoy 's gist and added some buttons which trigger the evaluation of the separate bins. See my fork. It's funny to watch on the system console.

Is there some caching going on with evalNWBin?

By the way, I noticed that executing evalNWBin from the developer console does not work.

[kilgaloon]

I can confirm that also when i start app and momentally open developer console, brhavior will be same like its not included.

[ghostoy]

You can send mail to me cong.liux#gmail.com

Strahinja [email protected]于2016年8月4日周四 18:38写道：

Project is kinda big, can you give me some where i can privately share it
with you?

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#5168 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAczeNW-FqImhTD51W_jTyudpJq7DUIdks5qccEpgaJpZM4JY06U
.

[ghostoy]

@rogerwang I can reproduce this issue with 0.14.6 and 0.16.0.

I've updated my gist @ https://gist.github.com/ghostoy/183649c64060b088a610ebc142fae3d2.

Steps to reproduce:

• build foo.js and bar.js with nwjc
• launch the app. test() run for first time at start.
• click "test" button. test() will run again.
• watch the output in console

This issue seems to be more easier to reproduce on 0.16.0.

On 0.14.6, it only produces the logs from later script, i.e. bar.bin, when run test() for a second time.

[27680:27680:0805/122054:INFO:CONSOLE(15)] "evalNWBin(null, '/home/user/Workspace/test/nwjc-test/foo.bin')", source: chrome-extension://oaohmlchfoanhbkbdhppgoadbhammijj/index.html (15)
[27680:27680:0805/122054:INFO:CONSOLE(0)] "foo", source:  (0)
[27680:27680:0805/122054:INFO:CONSOLE(15)] "evalNWBin(null, '/home/user/Workspace/test/nwjc-test/bar.bin')", source: chrome-extension://oaohmlchfoanhbkbdhppgoadbhammijj/index.html (15)
[27680:27680:0805/122054:INFO:CONSOLE(0)] "bar", source:  (0)
[27680:27680:0805/122056:INFO:CONSOLE(15)] "evalNWBin(null, '/home/user/Workspace/test/nwjc-test/foo.bin')", source: chrome-extension://oaohmlchfoanhbkbdhppgoadbhammijj/index.html (15)
[27680:27680:0805/122056:INFO:CONSOLE(0)] "bar", source:  (0)
[27680:27680:0805/122056:INFO:CONSOLE(15)] "evalNWBin(null, '/home/user/Workspace/test/nwjc-test/bar.bin')", source: chrome-extension://oaohmlchfoanhbkbdhppgoadbhammijj/index.html (15)
[27680:27680:0805/122056:INFO:CONSOLE(0)] "bar", source:  (0)

And on 0.16.0, it always produces the logs from former script, i.e. foo.bin:

[27817:27817:0805/122147:INFO:CONSOLE(15)] "evalNWBin(null, '/home/user/Workspace/test/nwjc-test/foo.bin')", source: chrome-extension://oaohmlchfoanhbkbdhppgoadbhammijj/index.html (15)
[27817:27817:0805/122147:INFO:CONSOLE(0)] "foo", source:  (0)
[27817:27817:0805/122147:INFO:CONSOLE(15)] "evalNWBin(null, '/home/user/Workspace/test/nwjc-test/bar.bin')", source: chrome-extension://oaohmlchfoanhbkbdhppgoadbhammijj/index.html (15)
[27817:27817:0805/122147:INFO:CONSOLE(0)] "foo", source:  (0)
[27817:27817:0805/122151:INFO:CONSOLE(15)] "evalNWBin(null, '/home/user/Workspace/test/nwjc-test/foo.bin')", source: chrome-extension://oaohmlchfoanhbkbdhppgoadbhammijj/index.html (15)
[27817:27817:0805/122151:INFO:CONSOLE(0)] "foo", source:  (0)
[27817:27817:0805/122151:INFO:CONSOLE(15)] "evalNWBin(null, '/home/user/Workspace/test/nwjc-test/bar.bin')", source: chrome-extension://oaohmlchfoanhbkbdhppgoadbhammijj/index.html (15)
[27817:27817:0805/122151:INFO:CONSOLE(0)] "foo", source:  (0)

[kilgaloon]

Good you reproduced this, one more thing to mention, there is also no difference if you put them in loop or you put them like this (using @ghostoy gist):

nw.Window.get().evalNWBin(null, process.cwd() + '/foo.bin');
nw.Window.get().evalNWBin(null, process.cwd() + '/bar.bin');

When i do this to more bins, same thing happen, first always get evaled n times where n = evalNWBin functions.

[kilgaloon]

@ghostoy @rogerwang Is fix for this going to happen anytime soon? im just curious.

[mscreenie]

@ghostoy Can bins be loaded via http or https urls?

[ghostoy]

@mscreenie No. Currently only supports local files.

[mscreenie]

Thanks should I open something to request that as a feature?

[ghostoy]

@mscreenie Yes, thanks.

[rogerwang]

@kilgaloon will fix it soon around 0.17 release, which will happen soon.

[kilgaloon]

@rogerwang Nice to hear that. Can't wait.

[rogerwang]

This is fixed in git and will be available in the next nightly build.

The root cause is NW is using previous cache of code.

[kilgaloon]

Great, nice to hear that, my project has been stalling because of this issue. Can't wait to see this working. Thanks

[prominentdetail]

I have this issue on 0.14.7 LTS
I can't use 0.17

[namaljayathunga]

I still have this issue on 0.14.7 LTS. Please fix this issue. thanks

[xianlong1226]

Due to our system to support the xp, we have to use 0.14.7 version, please repair this version as much as possible.