Jamal,
Just use Window.Process.ModuleName for the executable name without the
extension. Or use Window.Process.OriginalFilename for the executable
with the extension. If you use ModuleName then you can just add ".we"
and you've got the correct .we file for this application.
Of course Window is whatever you want it to be. for example it could be
the ActiveWindow or the FocusedWindow or whatever. The key is going to
the process of the window and getting that name so it doesn't matter
what window you use in that process space.
Doug
Jamal Mazrui wrote:
I have noticed that the module name of the focused window may be different
than that of the active window, e.g., in IE6. What is the most
authoritative way of getting the name of the module (and hence the .we
file) that caused the current set file to become active?
Jamal
--
Doug Geoffray
GW Micro, Inc.
Voice 260-489-3671
Fax 260-489-2608
http://www.gwmicro.com
