There is an anomaly with the “last” keyword. It is not reliable with groups.
Craig
> On May 25, 2024, at 8:03 PM, Bob Sneidar via use-livecode
> wrote:
>
> As I said, the last ID is going to be the stack ID -1.
>
> Sent from my iPhone
>
>> On May 25, 2024, at 16:55, Bob Sneidar wrote:
>>
As I said, the last ID is going to be the stack ID -1.
Sent from my iPhone
> On May 25, 2024, at 16:55, Bob Sneidar wrote:
>
> sounds logical, but I'm not sure, maybe you could store the ID of the last
> group somewhere.
___
use-livecode mailing li
IDs are assigned according to the stack ID which increments by 1 every time an
object is created. So yes, the stack ID is like an auto increment column in
SQL. It assures that no two objects get the same ID, and the last object
created is the highest ID in the stack.
Sent from my iPhone
> On
Hi jbv,
> Am 25.05.2024 um 16:20 schrieb jbv via use-livecode
> :
>
> Hi list,
>
> I have a script that creates groups on the fly
> with the command "group". These groups contain
> various flds and imgs.
> Can I always assume that the group with the highest
> id # is the last one created ?
sou
Last. "The last keyword <> can be used to specify any object <> whose number <>
property <> is equal to the number of objects <> of that type. It can also be
used to designate the last chunk <> in a chunk expression <>."
> On May 25, 2024, at 10:20 AM, jbv via use-livecode
> wrote:
>
> Hi lis
Hi list,
I have a script that creates groups on the fly
with the command "group". These groups contain
various flds and imgs.
Can I always assume that the group with the highest
id # is the last one created ?
Thanks,
jbv
___
use-livecode mailing list
u
