Well an object that appears on multiple cards will of course show up multiple times when you go from card to card. That is why my function ignores duplicates. But it is all probably quite moot anyway, at least for ID's because the vast majority of people don't care about them. So I wrote my function to return a list of any property you give it.
In retrospect, I did not account for properties that are arrays, so I should actually build an array and return that. Back ina bit... Bob > Ah, I think I know why: It is quite possible to have a control with an ID of > 1004 on one card, > and another with an ID of 1004 on the next card. > > And, at that point, one can see that looking for the object with the highest > ID in the stack is pretty pointless. > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
