there's another option, which is to investigate the polygrid. i've been
messing with it, because it does seem to be faster than a dg.
but first, i don't think i can resist trying to see why this is breaking.
if i do (and, instead work on this app i'm working on), it will demonstrate
the sort of
Hi Mike,
I suspect some change was made in the Datagrid scripts, such as a move
of some code from a stack to a script-only stack or some engine change
in how comparisons are done, variables interpreted, etc. that
inadvertently impacted the Datagrid code, but while we use a lot of
Datagrids,
On 12/13/2022 5:26 PM, Mike Kerner via use-livecode wrote:
here's something fun for you to try:
run the script twice. example: take the stack you submitted with the bug
report and execute preOpenStack from the message box, after the initial
failure.
It still fails for me under rc2, but I get
is this in a built app or interpreted?
the "silent fail" has been a feature of LC apps on mobile for a decade.
i wonder if these issues are both caused by some stack moving from binary
to SOS. the ask dialog certainly was migrated to an SOS, recently.
i see you included a recipe stack in the bug
Running your sample stack, I get an "error in object expression" at line
4793 in handler "_table.CreateHeaders" of stack
"RevDataGridLibraryBehaviorsDatGridButtonBehavior".
Seems to be because sResourceStack is empty.
Not sure if this is any help.
--
Mark Wieder
ahsoftw...@gmail.com
On 12/13/22 17:59, Mark Wieder via use-livecode wrote:
Running your sample stack, I get an "error in object expression" at line
4793 in handler "_table.CreateHeaders" of stack
"RevDataGridLibraryBehaviorsDatGridButtonBehavior".
Seems to be because sResourceStack is empty.
Not sure if this is
Anyone else having problems with:
set the dgProp["someProperty"] of grp "someDatagrid"
under LC 9.6.9rc2 vs LC 9.6.8?
In bug https://quality.livecode.com/show_bug.cgi?id=24046 were seeing
lines of script where we set the dgProp of a datagrid just stop (like it
hit and 'exit to top'). The
here's something fun for you to try:
run the script twice. example: take the stack you submitted with the bug
report and execute preOpenStack from the message box, after the initial
failure.
On Tue, Dec 13, 2022 at 5:21 PM Mike Kerner
wrote:
> there's another option, which is to investigate the
