nw.js window.on() not registered if app started as hidden

[anjanapaulose]

I am using nw 0.14.5 version.
I have to start the nw app in tray mode. I have defined the "on" function for "focus" as

var win= nw.Window.get();
win.on("focus", function(){
win.show();
});

and for tray click,

tray.on('click', function() {
win.show();
win.focus();
});

Now when I click on tray, the app comes into view as normal. I also have a shortcut to this app in start menu.

The issue is as follows:

The app is started as tray. I clicked atleast once on tray and app has came into view atleast once. Minimize will reduce the app to tray.
After this, if i try the startmenu shortcut, app comes into view as expected.

But if the app is started as tray, and I have never clicked tray, which means the app has never come into view.
In this case, if I try the start menu shortcut, the win.on("focus") code is never getting triggered, failing the app to show up.

If the app is already displayed atleast once, this issue is not seen. The window object itself is not defined unless the app is shown once.

Is there any condition like the win.on("focus") or such events are registered only when app is shown.
Please suggest a solution to this.

[anjanapaulose]

Hi, any updates on this bug?

[ghostoy]

What do you mean by 'try the start menu shortcut'?

[anjanapaulose]

Just create a exe which brings the running nw to focus.
Sample:

using System;
using System.Collections.Generic;
using System.Diagnostics;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.ComponentModel;
using System.Runtime.InteropServices;

namespace Sample
{
class Program
{

    [DllImport("user32.dll")]
    private static extern
    bool SetForegroundWindow(IntPtr hWnd);
    [DllImport("user32.dll")]
    private static extern
    bool ShowWindowAsync(IntPtr hWnd, int nCmdShow);
    [DllImport("user32.dll")]
    private static extern
    bool IsIconic(IntPtr hWnd);

    static void Main()
    {            
        var currentSessionID = Process.GetCurrentProcess().SessionId;
        Process[] processes = Process.GetProcessesByName("nw");           
        int currentProcID = Process.GetCurrentProcess().Id;
        Process[] nwInThisSession = (from process in processes where process.SessionId == currentSessionID && process.Id != currentProcID select process).ToArray();
        if (nwInThisSession != null && nwInThisSession.Length > 0)
        {
            int SW_RESTORE = 9;                              
            foreach (Process p in nwInThisSession)
            {
                if (!string.IsNullOrEmpty(p.MainWindowTitle))
                {
                    IntPtr hWnd = p.MainWindowHandle;
                    if (IsIconic(hWnd))
                    {
                        ShowWindowAsync(hWnd, SW_RESTORE);
                    }
                    // bring it to the foreground
                    SetForegroundWindow(hWnd);
                    break;
                }
            }
        }          

    }
}

}

[ghostoy]

@anjanapaulose I haven't tested your C# app. But I think IsIconic is used to test if windows is minimized not invisible. So could you try test with IsWindowVisible and call ShowWindowAsync with SW_SHOW or SW_NORMAL?

[ghostoy]

@anjanapaulose Does my suggestions work for you?

[anjanapaulose]

Sorry for the delay, tried as per your suggestion. Didn't work.

[ghostoy]

Could you upload the entire project of your C# testing app so that I can test with?

[anjanapaulose]

I was unable to upload the whole project as zip, it was failing. Please see the attached txt file, rename it to Program.cs. I used a Visual Studio project with output as exe. Please go though the comments added to know which case is working for what scenarios.

Program.txt

[ghostoy]

This should be the limitation of Windows API. See http://stackoverflow.com/questions/16185217/c-sharp-process-mainwindowhandle-always-returns-intptr-zero.

A process has a main window associated with it only if the process has a graphical interface. If the associated process does not have a main window, the MainWindowHandle value is zero. The value is also zero for processes that have been hidden, that is, processes that are not visible in the taskbar. This can be the case for processes that appear as icons in the notification area, at the far right of the taskbar.

[anjanapaulose]

Thanks, I am not so familiar with windows processes, just a doubt

"The value is also zero for processes that have been hidden, that is, processes that are not visible in the taskbar. "

So if the process is in task bar, it should come up, right?. So in this case, it will always come once its clicked. Whats the difference if tray icon is once clicked and not.

[ghostoy]

@anjanapaulose I'm confused. Here is following you addressed previously.

But if the app is started as tray, and I have never clicked tray, which means the app has never come into view.

I assume it means the window is hidden on start since "the app has never come into view" and the title of this issue is "... if app started as hidden". In this case, there will not be a taskbar icon, and you will not get the window's handle or title.

[anjanapaulose]

Ohh, yes, that is one case. If the app itself is started as hidden, it will never come into view.

I have also seen the below scenario.
If I start the app as tray, the program doesn't work unless I click on tray once. This means app is in tray, still I cant use the shortcut. Once I click tray, and app comes into view, then onwards the shortcut works even if the app is hidden as tray(not minimized). You could try that with the same sample app

[ghostoy]

@anjanapaulose If it's hidden and only shown in tray, you will not get the window handle and get it shown. That's the limit of Windows API. If it's minimized as icon in the task bar, then your shortcut will work.

[anjanapaulose]

Ok, thanks for the clarification.