#221 Window Info: Invalid process names

[xanda escuyer]

The process name is incorrectly reported under the 'Window Info' dialog box (obtained by middle-clicking the title bar).
This is a problem because it breaks any window rule that subsequently relies on it. For example, window information for the following apps is yielded as:

[VLC Player]
Class Name: QWidget
Window Name: VLC media player
Process Name: ?ÿ

[Tight VNC Viewer]
Class Name: #32770
Window Name: New TightVNC Connection
Process Name: ?µtsŒ

Even though it is still possible to manage these windows effectively (by relying solely on class), it makes browsing the rules list somewhat tricky because of its cryptic display.

We have tried editing the rule to include the full path to the executable but this doesn't make any difference.

Is this an error or simply a limitation of the software? If the latter, then please can a comments field be added to each entry on the rules list to assist admin?

Thanks for reading - love using VirtuaWin.

Platform details:
Windows 7 Ultimate x64

[Steven Phillips]

It looks to me like you are using the standard version (VirtuaWin_setup_4.4.exe or VirtuaWin_portable_4.4.zip) rather than a unicode version which supports multibyte characters (i.e. VirtuaWin_unicode_setup_4.4.exe or VirtuaWin_portable_unicode_4.4.zip). Can you please confirm which version you are using and if its not one of the unicode versions please reinstall with one of these.

[xanda escuyer]

Thanks for responding.
We have indeed been using the standard version which presents this issue.
We have now reinstalled (while clearing out settings to boot) using the unicode version.
Now the problem has mutated to something else: the process name for programs is empty, otherwise shown as <unknown>. This appears to be an issue only with 64 bit apps though.
32 bit programs as run from C:\Program Files (x86)\ are displayed accurately.
Thanks again for your time.

[Steven Phillips]

I can reproduce this issue in the standard VW as well, will try to fix.

[xanda escuyer]

Hello again, Is there any progress on this? Thanks.

[Johan Piculell]

Hi. Probably not, I did however get a similar report via mail a few weeks ago which I think is the same issue, and also a solution to it:

"this seems to be a 64-bit issue. GetModuleFileNameEx() does not return the module name if called from a 32-bit application for a 64-bit process. QueryFullProcessImageName() does not have this problem."

Will see if I can take a look at this later this week, Steve is probably fully occupied still.

Regards
/Johan

[Steven Phillips]

Fix submitted and will be in the next release.

[xanda escuyer]

Is there any chance we can this fix released please?
Thanks.

[xanda escuyer]

Thank you - we look forward to it.

Steven Phillips bjasspa@users.sf.net wrote:

Fix submitted and will be in the next release.

[bugs:#221] Window Info: Invalid process names

Status: open
Group: v4.5
Created: Fri Jun 07, 2013 02:36 PM UTC by xanda escuyer
Last Updated: Sun May 18, 2014 08:11 PM UTC
Owner: Steven Phillips

The process name is incorrectly reported under the 'Window Info' dialog box (obtained by middle-clicking the title bar).
This is a problem because it breaks any window rule that subsequently relies on it. For example, window information for the following apps is yielded as:

[VLC Player]
Class Name: QWidget
Window Name: VLC media player
Process Name: ?ÿ

[Tight VNC Viewer]
Class Name: #32770
Window Name: New TightVNC Connection
Process Name: ?µtsŒ

Even though it is still possible to manage these windows effectively (by relying solely on class), it makes browsing the rules list somewhat tricky because of its cryptic display.

We have tried editing the rule to include the full path to the executable but this doesn't make any difference.

Is this an error or simply a limitation of the software? If the latter, then please can a comments field be added to each entry on the rules list to assist admin?

Thanks for reading - love using VirtuaWin.

Platform details:
Windows 7 Ultimate x64

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/virtuawin/bugs/221/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/