Without knowing exactly what you're trying to accomplish, one way is to display only a few rows of buttons beyond what will fit comfortably on a screen, and when scrolling takes place, "recycle" the rows around to the end (or beginning) with new glyphs applied.
Assuming all the characters are from a single font and you're trying to display glyphs in an organized fashion, a better way might be to display all the glyphs in a field with extra column and row spacing to essentially form a grid. This is how I display glyphs from icon fonts, which is more efficient than using thousands of controls on a card. Regards, Scott Rossi Creative Director Tactile Media UX/UI Design > On Apr 1, 2017, at 3:07 PM, Richmond Mathewson via use-livecode > <email@example.com> wrote: > > What a nuisance: > > There I was, merrily churning through the button titles for my Unicode > Reference thing > [ http://forums.livecode.com/viewtopic.php?f=26&t=29069 ] which needed at > least 1600 buttons > that were 23 pixels deep layered underneath each other. > > What happens? > > At the "Magic Number" of 32xxx I get a "this is not a number" message. > > As a result I ended up restricted to 1400 buttons. > > This is very bad as the Unicode glyph tables are many, and in an ideal world > I'd like 8703 buttons. But 8703 * 23 = 200169 > > That would involve groupig a "stack" of buttons that was 200169 pixels high. > > Would be grateful if anyone knows a way to circumvent the limitation. > > Richmond. > > _______________________________________________ > use-livecode mailing list > firstname.lastname@example.org > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list email@example.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode