Nw.js: Pinning app in taskbar is creating an incorrect shortcut target

[sumit6b]

NW.js v0.21.6
Windows 7 Professional

I am running my app by executing a command <directory-nw>/nw.exe <directory-package.json> .
Now from the task bar when I right click and choose "pin this program to taskbar" I get a shortcut whose target does not contain the first parameter which I used to start the process, i.e, target only has <directory-nw>/nw.exe. So when I try to open my app using this shortcut, default window of nwjs gets displayed.

I tried using --nwapp argument but it is not opening the app whose directory I am passing as the value of this argument.

[Christywl]

1. Same result for me on Windows
2. I also find another problem:
   Open a sample app(named 'test') with nwjs and pin it to the taskbar, right-click the icon, and the name is 'test', not nwjs or NWJS Default. If you open the window with this icon, it will open the nwjs default window with another icon(not nwjs default icon) in the taskbar. I think this may be an issue.

@rogerwang , could you please help confirm this ?

[taher]

@rogerwang The issue is specifically when the app package is in a different folder than the nwjs binary ... and the path to app (folder which has package.json) is passed as command line argument.

On pinning to taskbar, the shortcut target doesnt have path to app argument, which makes the app broken. Since this is the most visible shortcut for the users... they are not able to launch the app again once they pin shortcut to taskbar.

[semmel]

With NWJS v. 0.25.5 this issue may be fixed partly. I can no longer confirm that when pinned to the taskbar the exe parameters are missing.

When running the app from the pinned taskbar icon I find in the array nw.App.argv the same parameters which were given to MyApp.exe on the initial launch from a desktop shortcut or by console command.
However the nw.App.argv array contains additional items (--profile-directory and --app-id) which should just show in nw.App.fullArgv. So I guess taskbar pinning is still a little buggy here.

In my case I employ the --user-data-dir=%APPDATA%\MyApp parameter to direct the user data to the Windows Roaming folder. Previously this did not work when the user pinned my app to the taskbar, but with nwjs 0.25.5 it works now fine.

@Christywl Regarding the app title in the taskbar I cannot confirm this either. It looks ok now for me:

In my manifest: "name": "TestApp"

Test System:

• Win 10 x64
• nwjs 0.25.5 (nightly)
• MyApp.exe is nw.exe glued with package.nw (html sources zip file) via copy /b

[tphalp]

Same issue here. On v0.29.3 of nwjs.

When pinning to taskbar, lunching the app results in the NWJS window only. Same situation as @taher. App package (folder) is in a different location that the nwjs binary. The original shortcut that we install with the app passes the location to the binary, but when pinning, the shortcut for the pinned app doesn't have the package location in the shortcut.

[rogerwang]

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