>I checked the code. The only property that can cause this is oObjectUnderMouse and I think I handle it correctly. I don't see how...
>
-- snip --

Vlad:

Yes there are certainly more people using fancytooltips. I do and like it very much.

I have experienced the failure of a form to release. It did not occur to me that fancytooltips might be the cause. I'll look at it again.

I am also experiencing the situation where the first display of fancytooltips upon show()ing a form is truncated to the first few letters -- the same error Valadimir reports. It is not a particular problem if you do not turn on fancytooltips until after the form is show()n.

It is a clever tool, congratulations. The only change I made to your older version was to install a ShowFancyTips property in the form to control display of the tips, a menu item to control the type of fancytooltip displayed and turn it off and on, and a few lines of code to suppress display if the objecunderthemouse is also the active control. I also moved the display closer to the top or bottom of the objectunderthemouse so it would not interfere with reading the value of the control.

I am now looking at some way of displaying the fancytool tip without using a timer -- using the mousemove() event, maybe, since the timer can sometimes interefere with the display of selected text. Specifically where a textbox is displaying numeric data, the timer seems to switch the display from its actual value to zero then back again. This only occurs if the numeric value is selected. I have not yet tracked down why this is so.

Anyway, congratulations on a useful and elegant tool. I am certain there are a lot of developers using it.

Regards,

JME