programmerdelphi2k 237 Posted March 20, 2023 I'm not intimate with the depths of MSWindows, but I think the TLabel might respond to the "CM_TEXTCHANDED" message, so you can do some checking by redrawing the control (invalidating it and resetting to the new text) Share this post Link to post
peardox 0 Posted April 16 I was just having this problem and found a nasty explanation (bug) I was calling Main Form via a custom event handler to pass some data I want to monitor but the electric just had to be switched off (highly relevant) so I set my Laptop to being only monitor and suddenly I was seeing numbers changing without any kind of special processing. Electric came back on so I switched back to Laptop + External monitor and it stopped working again (External being main display). Running it again I dragged to form between displays - on Laptop screen numbers change, on External display they don't ... As some will have multiple displays (most these days?) it is likely that some people will think it works and some people wont Note that like the OP I'm also using FMX Share this post Link to post
Remy Lebeau 1394 Posted April 16 (edited) On 3/20/2023 at 12:16 PM, programmerdelphi2k said: I'm not intimate with the depths of MSWindows, but I think the TLabel might respond to the "CM_TEXTCHANDED" message, so you can do some checking by redrawing the control (invalidating it and resetting to the new text) CM_TEXTCHANGED is a VCL message, it doesn't exist in FMX. When the TLabel.Text property is changed in FMX, there is no window message issued back to the TLabel, but there are virtual methods called instead, such as DoChanged() and DoTextChanged(). It should also be mentioned that the Text setter already calls Repaint() after calling the virtual methods. Edited April 17 by Remy Lebeau Share this post Link to post