workaround for cut-off text in native scroller?

Klaus major-k klaus at
Tue Jun 1 14:14:09 EDT 2021

Hi Brian,

> Am 01.06.2021 um 17:09 schrieb Brian Milby via use-livecode <use-livecode at>:
> One thing to try for testing would be to use FSM of empty

Sorry, no idea what "FSM of empty" might be? :-)

> and see how many lines are required.  

Will do, once I know what it means!

> One thing I noticed with browser widget is that native elements render at device resolution inside regardless of FSM in use.  If it requires the same, then this is probably not related.  If the number changes, then I may be on to something.  In either case, having to fudge the height of a text field is not good.



Klaus Major
klaus at

More information about the use-livecode mailing list