forum.vdsworld.com

[jules]

Ah, I'd got out of the habit of checking for replies there.

I have now, and I'll take a look at you code when I get a chance. Hopefully it will give me the clue I need as to why the tips disappear forever after you click them.

[jules]

Thanks. That did help. I don't have the problem of tooltips disappearing forever when you click them any more, but because I now have only one tooltip control per window, like you did, and add the tips for each element to that control, they all have to be the same style (i.e. normal, multiline or balloon) and have the same title and icon. The way I'd been trying to do it, each element had its own tooltip that could be whatever style, colur and so on that you like.

It seems to me that perhaps I don't understand how people want to use tooltips. Microsoft implemented it this way, so presumably people will want to choose one style for all the tooltips on a window. Is that right? I see now that CodeScript's DLL is also doing it this way, although because I couldn't see the actual code he used, I didn't realise it at the time.

But I don't want to add a new "Tooltip" dialog element separate from the other elements, just to allow for different styles, because it seems more complicated and non-intuitive, because it seems logical to me that each tooltip belongs to a particular dialog element, even though that isn't how Microsoft has implemented it.

[vdsalchemist]

Jules,
I wrote that code more than a year ago but if memory serves me right the reason you are probally having the issue is because under windows the tooltip is a shared resource for the full dialog. Your dialog elements in the main dialog are child windows to the parent so even if you assign a tooltip to that child window the tooltip is still a child window to the main parent window as well. I for one have not really seen application windows that have different styled tooltips for each child window or control. I think the only true way to do what you wanted to do is to either super-class the tooltip window or put one heck of a sub-class routine together

Main Dialog Window
|
|_VDS element
|
|_Tooltip element

[jules]

Yes, I didn't realise this because most of the Delphi examples just create a single balloon tip. I think I'm going to have to settle for doing what can work, because all this talk of super- and sub-classing is just gobbledygook to me. I don't understand much about API level programming; my approach has always been that if I can't find a Delphi component that does what I want I'll manage without it.

[vdsalchemist]

Hey that is fine by me. I personally think that programmers spend too much time on tooltips anyway Especially since most of the time users are just annoyed by them anyway hehehehehe