titlebar api hook

So is there a different hook we should be using, or is the exit on the tray icon just not doing an explicit unhooking.

I only know of global / local variables like in a small basic or c program ...

Are there such things as local hooks - not global hooks?   My understanding about how these hooks actually work is a little weak.

I am pretty sure that all the programmers I have talk to about this claim:
1.  A server side service to set a hook will not work, because the hook process needs to be running in each users space.  So we basically start up a trayhookicon for each citrix user that logs on to the box.  This seems a little heavy handed to me - having 10 processes instead of 1 system service running.

2.  Would it be better to load a service each time a user logs on?   Right now, because titlehooktray.exe icon loads, the citrix session never ends.  When the users exit the dental app from their seamless window there is no way for them to unload the tray icon, or kill titletrayicon...  I might have the same problem with a user level running service but I do not think user services attach to a particular citrix session like a small app does.

Other prgrogrammers have told me that it may or may not go away, even after being unhooked.

I see you are a guru several times over:
What specific recommendations would have to make this work as elegantly as possible?

I appreciate the time it takes to reply.

Thanks,
Greg

gsgi,
>>Are there such things as local hooks
Yes. They only hook activities of the running program (, i.e., titlehooktreay.exe) so are not useful for monitoring other programs.

>>the hook process needs to be running in each users space.
This is correct. I know nothing about using a citrix server, but a global hook DLL will need to be running on (what is effectively) the user's computer.

>>the citrix session never ends
This may be an unavoidable flaw in the current system. It is possible that the UnhookWindowsHookEx call in the uninstall() function might fail. I'm not sure about this... why it would fail, or how to avoid that potential failure.

>>What specific recommendations...
Sorry, but my best advice is this:
 Get rid of the entire hooking scheme.

From the code, it looks like all the hook does is look window captions with text matching part of two text strings. Rather than using a hook, just have a standalone application program use FindWindowEx or EnumWindows to look for matching caption text. The target window probably has a relatively-distinctive window class, which can be used to narrow the search. Use Spy++ to find out some unique characteristics of the target windows, and use that as part of your matching criteria.

Have it do that on a standard window timer -- say once every 10 seconds, or some other reasonable interval. Once a matching window is found, process the text (output it to the log file) and then save it in memory (you need to provide a means to avoid relogging it 10 seconds later).

Since this technique does not use a global hook, it will not inject itself into zillions of programs and will not cause session shut-down problems.

-- Dan