workaround for cut-off text in native scroller?
brian at milby7.com
Tue Jun 1 11:09:18 EDT 2021
One thing to try for testing would be to use FSM of empty and see how many lines are required. 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.
Sent from my iPhone
> On Jun 1, 2021, at 11:00 AM, Klaus major-k via use-livecode <use-livecode at lists.runrev.com> wrote:
> Hi Rick,
>> Am 01.06.2021 um 16:38 schrieb Rick Harrison via use-livecode <use-livecode at lists.runrev.com>:
>> Hi Klaus,
>> What happens if you add 100 blank lines?
> I get the white space of hundred empty lines in the scroller.
>> What happens if you add 100 blank lines and the last one has something on it?
> Did not try that.
>> I hope you find a suitable workaround because that’s a serious bug!
> Hm, not sure, but it looks like you need at least 5 empty lines to "fool" LC to compute
> the correct scroll of the native scroller. Means all lines are visible, but not the EMPTY lines!?
> And yes, this IS a serious bug!
> Klaus Major
> klaus at major-k.de
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode