What about having two fields with a small amount of overlapping (same) text and as the first field reaches the end of its scroll, the second field could be displayed and begin its scroll… —Scott
> On May 2, 2020, at 10:25 AM, J. Landman Gay via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I think the solution has to be in the engine. I'm in trouble. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > On May 2, 2020 2:27:53 AM scott--- via use-livecode > <use-livecode@lists.runrev.com> wrote: > >> I’ve run into that a few times but not recently. I couldn’t find anywhere >> that I had worked around it. All I can imagine trying is >> 1. Swapping text in and out at some point (possibly just one giant stutter) >> or >> 2. Changing the size of the text that is not visible during the scroll… >> though (the more I think about that one the more it seems like it would make >> the scroll wacky in other ways) Neither seems super-promising but that’s >> all I can think of at the moment. If you find a solution, I would love to >> know what it is. >> — >> Scott >> >> >>> On May 1, 2020, at 10:24 PM, J. Landman Gay via use-livecode >>> <use-livecode@lists.runrev.com> wrote: >>> >>> Yes, that seems to be the problem. I have a long text field that exceeds >>> the maximum. There's an enclosing group to be compatible with >>> acceleratedRendering on mobile. The same setup is used for all the >>> field/group combinations in the stack and they all work except this one, >>> but the others are all shorter. >>> >>> I set the inner field to its full formattedHeight inside the group, which >>> is shorter. The group has a behavior that scrolls the content. >>> >>> I discovered today that if I set the behavior on the field instead of its >>> enclosing group, I can make it scroll. But acceleratedRendering on a field >>> is jerky and doesn't work very well on mobile. I can't break up the text, >>> it has to be all one block. I have tried setting the group to container >>> layermode without success. >>> >>> If you're wondering why the text exceeds the maximum, this is for a mobile >>> app and there is not only a lot of heavy formatting with large headings and >>> spaceBelow, but the text size is largish so that it is readable on a tiny >>> phone. That makes the pixel count pretty high. >>> >>> I only have a very short time left to solve this. >>> >>> On 5/1/20 4:45 PM, scott--- via use-livecode wrote: >>>> Are you exceeding the maximum vertical scroll? >>>> (I haven’t run into this recently but I believe at one point the vScroll >>>> of groups was limited at the engine level to 32780) >>>> Scott Morrow >>>> Elementary Software >>>> (Now with 20% less chalk dust!) >>>> web https://elementarysoftware.com/ >>>> email sc...@elementarysoftware.com >>>> booth 1-800-615-0867 >>>> ------------------------------------------------------ >>>>> On May 1, 2020, at 1:17 PM, J. Landman Gay via use-livecode >>>>> <use-livecode@lists.runrev.com> wrote: >>>>> >>>>> Is the formattedHeight of a group broken for anyone else? LC 9.6dp4 (and >>>>> possibly dp3). >>>>> >>>>> I'm a little frantic. >>>>> >>>>> -- >>>>> Jacqueline Landman Gay | jac...@hyperactivesw.com >>>>> HyperActive Software | http://www.hyperactivesw.com >>>>> >>>>> _______________________________________________ >>>>> use-livecode mailing list >>>>> use-livecode@lists.runrev.com >>>>> Please visit this url to subscribe, unsubscribe and manage your >>>>> subscription preferences: >>>>> http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
