LiveCode Forums

monte wrote:If nobody else supports this then the pull request might as well be closed

I support it, Monte. Its syntax is, I think, a worthwhile improvement over invoking function RevRuggedID, and it deserves any attention it'll get in the dictionary (presuming the dictionary will be kept up).

-- Dick

... My point here is that if 'the rugged id' is toted as being the simplest reference needed to preserve what a control is, then it missing out the 'card' means it fails in this regard for controls that could be shared. Also, given that a control can go from being shared to non-shared and vice-vers...

... Either that or provide a way to get all the values for unshared properties.. like in an array keyed on card id... that would be handy for lcVCS actually... could I do that? You can. In the context of the following command, there are repeat loops for each card and control of a given stack. comma...

I've found a few use cases where I want to dispatch a message to an object but I only want that particular object to handle it... Another approach is to check whether the object implements the command before dispatching. filter the revAvailableHandlers of tObject with "M " & tCommand & " *" if it i...

It's so -%$#@- dark in this bikeshed! I can't believe they didn't include motion-sensing eco-friendly mood lighting in here.

@Dick - should the BNF pattern be more like this? [ [regex] [pattern] ] <pattern_exp> ... I assumed that "pattern" would be optional as well. If a developer is more comfortable writing "regex pattern" instead of "regex" to make the code more (for them) readable, then I don't think there should be a...

We could treat 'with' and 'matching' as synonyms, and of course likewise 'without' and 'not matching'. And to clarify the 'pattern' to use, we introduce 'wildcard' as adjective for the old filter pattern mechanism, and 'regex' for regular expression pattern matching. ... The BNF for this part of th...

filter [ { lines | items | items in lines } of ] <container_or_exp> { { with | without } <filter_pattern> | [ not ] matching [ pattern ] <regex_pattern> } [ into <container> ] A simpler form obviates introducing "matching," and negating it, instead introducing the simpler term "regex:" filter [ { l...