For a succession of selection Lists my script builds a group of several fields that can be scrolled inside of another group.
Scrollbar is applied when necessary via:
if the formattedheight of group "Buttons" > the height of group "Buttons" then
set the vScrollbar of group "Buttons" to true
else
set the vScrollbar of group "Buttons" to false
end if
That works real dandy most of the times, but in one situation that group becomes quite big and holds some 460 Items (far too many of course but for the moment …). In this case no scrollbar shows, switching it on doesn't help, and the content can not be scrolled by any other means and the formattedheight of group "Buttons" returns 0
I've checked the properties of the group, container and contents in this case against situations where it behaves as I expect, but there are no differences except text contents and individual positions.
Where do I go wrong - or is there an inherent Limit to group Size ?
Group Size Limit
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: Group Size Limit
Hi, the following I already reported as documentation bug (#11639).
May be this "hidden limit" applies to your problem.
== MEMO for Documentation ===== [-hh, Dec 31, 2013]
== LIMITS FOR ALL COORDINATES OF OBJECTS
Refers to
1. User guide pdf page 43 (section 2.2.9)
2. LCapp/Contents/Tools/Documentation/rev/Memory and Limits Reference.rev
In both above summaries of 'memory Limits' one IMPORTANT is currently
missing that in fact limits the size of ALL objects that have coordinates:
The value range -32768 to 32767 for coordinates.
Cited from the Docs, see for example the entry to 'height':
Note: The current architecture uses 16-bit signed integers for all
coordinates, which means that the value range is -32768 to 32767.
== End MEMO
May be this "hidden limit" applies to your problem.
== MEMO for Documentation ===== [-hh, Dec 31, 2013]
== LIMITS FOR ALL COORDINATES OF OBJECTS
Refers to
1. User guide pdf page 43 (section 2.2.9)
2. LCapp/Contents/Tools/Documentation/rev/Memory and Limits Reference.rev
In both above summaries of 'memory Limits' one IMPORTANT is currently
missing that in fact limits the size of ALL objects that have coordinates:
The value range -32768 to 32767 for coordinates.
Cited from the Docs, see for example the entry to 'height':
Note: The current architecture uses 16-bit signed integers for all
coordinates, which means that the value range is -32768 to 32767.
== End MEMO
shiftLock happens