On 11/04/2016 02:28 PM, Bart via Lazarus wrote:
On 11/4/16, Ondrej Pokorny via Lazarus wrote:
The TextHint implementation should be completely rewritten. It shouldn't
use the text property but paint the TextHint onto the control by itself.
Windows can do that
On 04.11.2016 13:16, Luiz Americo Pereira Camara via Lazarus wrote:
In the last trunk, the slow issue is fixed regardless of usage of
TextHint in TMemo or not. Fixed also not being reset after text
changed / added
I see that r53292, r53293 and r53296 are all about TextHint - all this
code
In the last trunk, the slow issue is fixed regardless of usage of TextHint
in TMemo or not. Fixed also not being reset after text changed / added
Due to the way CharCase is implemented, the slow will manifest if this
property is set to a value different from the default one
Some notes:
- It
On 04.11.2016 10:38, Michael W. Vogel via Lazarus wrote:
Thats also fine. So it can be implemented for TComboBox (as in Delphi)
too.
Yes, exactly.
So for now, the speed and paint issue should be fixed, later the redesign.
If the issue is a direct cause of introducing the TextHint property
On 2016-11-04 07:35, Ondrej Pokorny via Lazarus wrote:
> The TextHint implementation should be completely rewritten. It shouldn't
> use the text property but paint the TextHint onto the control by itself.
Very true, and using the Tex property for that is indeed a very bad
idea/design. fpGUI's
2016. 11. 04. 8:35 keltezéssel, Ondrej Pokorny via Lazarus írta:
The TextHint implementation should be completely rewritten. It shouldn't
use the text property but paint the TextHint onto the control by itself.
It's good to hear! The new implementation will be included in 1.8?
Gabor
--
On 03.11.2016 22:46, Michael W. Vogel via Lazarus wrote:
1. TextHint in Delphi is theme dependent and OS dependent (available
for Windows Vista, Windows 7, or later), in Lazarus not. What is the
desired behaviour?
TextHint in Lazarus should be OS independent (it was decided long time ago).