Hello Brendan. Users are lazy and they don't read the manual so I force them to learn something on the way, by setting detailed tool-tips to almost every single button I put on my applications. I also give then the chance to set the timings for tool-tips. It will be great a better THintWindow that will auto increase the 'stay on screen' time depending on the length of the hint/string. This way, the hint will stay longer on the screen, if it has more text to display.
I also used the solution you suggested but only in few occasions since it can't be used heavily in a big project because the management of the tool tips (documentation) is difficult when you don't remember (at design time) if you set a hint or not for a specific VCL and if you don't see the hint unless to browse for it. Cubic __________________ Brendan Blake wrote: > I've always written code to set the hints when they are sufficiently > long that they need to be split, for example: > Image1.Hint:='This is line 1 of the hint'+#13+' and this is line 2'; > > It can be done in FormCreate, and I don't think there is any significant > performance disadvantage compared with using the property editor > > This way you can also have a dynamically created hint that is context > sensitive, depending on (for example) the mouse position. > > Brendan Blake. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of CubicDesign > Sent: 27 June 2007 18:32 > To: [email protected] > Subject: Help needed with RegisterPropertyEditor > _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
