Tooltip ques



Hi
I've seen a couple net samples for making tool tips.
They give the ability to show a tool tip over a control on the form in your
own app.
I'm wondering if there's a way to show a tool tip when cursor is over
another app,
with which my app is connected and interacting, maybe somehow by creating an
invisible window which could then get a hwnd which could then receive the
tooltip???

I don't know enough about creating windows via api to know if this is
possible or not.
I would need to somehow track the cursor's movement, detect when it fell
over certain objects in the external app, (autocad window), and then
depending on the object, show a tool tip with whatever message.

Thanks for any ideas
Mark


.



Relevant Pages

  • Re: SendKeys Method when Computer is Locked
    ... "handle" of the child window you are interested in. ... unless the control has focus, ... app to respond. ... Personally I prefer the system api approach. ...
    (microsoft.public.scripting.wsh)
  • Re: Automated GUI testing
    ... Having this ideas in mind you can succeed if you control the program ... naming can make your job of locating the proper window and control ... >1) Window Definitions Scripts ... This definition must be 'tied' to the actual app windows, ...
    (microsoft.public.vc.mfc)
  • Re: Steve Carroll does not know the difference between saving and quitting.
    ... or in an app where it can be used for additional work it ... Most apps cannot be used with no window open... ... yet it does not quit. ... And nor should it Snit! ...
    (comp.sys.mac.advocacy)
  • Re: MORE Lyle Blake Info......
    ... >control with a static window beside it to show the percentage. ... The lightweight controls will be part of the DLL ... unloaded - the DLL might be unloaded without the App terminating ...
    (comp.lang.pascal.delphi.misc)
  • Re: Window closed event?
    ... You can then add a method to notify the user control ... >>> In a windows forms app how do you know a window is closing? ... >>> I have timer object that appears to be firing after the window is ...
    (microsoft.public.dotnet.framework.windowsforms)