Hi Daniel,

This is of course also a legitimate, and interesting, point of view. :)

I'll keep it in mind.

>Hi Peter,
>
>I have no perfect answer to your question. But I bumped on a similar issue when trying to improve the "user experience" on a large highly intensive picture (a map) on display with a VFP form.
>
>We were using the VFP tooltip as a way to convey information about every control on the form. But a smart user of the application mentioned that using "windows TOOLtips" as a way to convey information about data was possibly not adequate. As he said tooltips SHOULD be tips about the tool not information about the data itself. In his view, tooltip contents should NEVER be changed... I reckon he was/is right. At least as far as our app was concerned. We were possibly wrong trying to change tooltip text at runtime!
>
>I hope I was clear enough. Difficult to say more. What we did in the end? We kept all our tooltips in their use as information about the behaviour of each and every "widget" (help support) but we decided to replacei our dynamic tooltips with "information tips" when bringing information on large data container controls such images or as grids. In such cases, we add what we call "data tips". They bear some resemblance with tooltips but we made sure they are a bit more dynamic (faster to display and disappear) and may contain bitmap information at times as well.
>
>These information-centric "data tips" are currently based on the vfp picture base class. But they could of course be based on any control that you feel is suitable including simpler text or anything suitable. I understand that my answer is generic not VFP specific and possibly not up to the exact point you made. But I found this user comment to makes sense for us!
>
>Daniel