In this particular case, the table being displayed in the polygrid is
based on datasets that researcher loads into our application and the
number of rows and columns can vary widely as well as the column
names/labels and type of data. Rather than conduct a large analysis to
determine which of
Why not get the pgColumns first, alter only the array element needed for the
specific column(s), then set the pgColumns of the PolyGrid?
Bob S
> On Aug 24, 2023, at 1:26 PM, Paul Dupuis via use-livecode
> wrote:
>
> Thanks Klaus.
>
> I may use this method rather than the overhead of
Thanks Klaus.
I may use this method rather than the overhead of clearing and setting
the whole pgData property.
Actually, the more I think about it, neither "method" should be needed.
This is a polygrid bug. If you set the pgColumsn to fewer column,
regardless of whether there is left over
Hi Paul,
> Am 24.08.2023 um 20:30 schrieb Paul Dupuis via use-livecode
> :
>
> Aha, I was setting pgColumns to the fewer columns and THEN pgData to the
> smaller data set to match the columns
> You need to clear the pgData (set to empty) first, then set the columns, then
> set the new pgData.
Aha, I was setting pgColumns to the fewer columns and THEN pgData to the
smaller data set to match the columns
You need to clear the pgData (set to empty) first, then set the columns,
then set the new pgData.
Perhaps this is a documentation bug?
On 8/24/2023 2:26 PM, Paul Dupuis via
Hi to any polygrid developers out there,
Please see bug https://quality.livecode.com/show_bug.cgi?id=24315
I have run into an issue with the latest polygrid (as of this post)
where if you set pgColumns to a new array that reduces the number of
columns in the grid, some old columns are not
