LiveCode Forums

I like the idea. I actually threw a stack together last night to test/verify flow. That side route should be “not in” but before/after still will get called. If you pass in the object, then both “on” handlers will fire before the “after” one will. If you pass in the behavior, then the “after” will ...

Thanks for the share Brian!

On an unrelated note, I see GitHub views your code as 100% HTML, which is mildly aggravating...
When will LC push for their language to be recognised as such on GitHub?!?!?!

Generally I'm not sure you can use the custom props as an array as is and have found I have to put them into their own array.
This should work:
S.

Well arguably, StartUp is still an event, so not sure that merits its own header - can't list every single event generated in LC! I presume StartUp bypasses the frontScripts, as it's sent to card 1, but not sure... The 3 annotated events here are special inasmuch as they can bypass the default path....

I like having them in the muted color like your last one. I think an info box at the bottom with some of the caveats that should be considered would work. Behaviors support the before/after control structures which allows developers to produce behavior scripts which can handle messages sent to a co...

As a solution to that last point, I’ll change the “from other stacks” to “from other message paths”. Hopefully this will reduce confusion?

As to the former, given that I would like this as visual as possible, I think I’ll ad a small inset graph showing before/default/after, that may work better…

I like having them in the muted color like your last one. I think an info box at the bottom with some of the caveats that should be considered would work. Behaviors support the before/after control structures which allows developers to produce behavior scripts which can handle messages sent to a co...

I’m not sure you can really represent behaviors cleanly like that. They don’t sit where they are drawn completely. In addition to catching messages that are not present in the object you can also have “before” and “after” handlers that fire before/after the handler in the object. Thanks Brian, The ...

Klaus wrote: ↑

Tue May 07, 2024 4:39 pm

Don't you read the previous postings?
LC 9.6.11 is the latest stable version.

Still might be worth checking to see if also present using 9.6.12 (RC1) and/or 10.0.0 DP8, there's a number of fixes in those...

To my surprise, when I attempted to add a "mouseUp handler script" to the Script Widget in the stack, it failed to trigger :?: What do you mean by this? Do you mean adding a handler to the built widget's script window? Or inside the scriptOnlyStack that builds the widget? If it's the former, you pr...

Jeff, it doesn't seem to be your code - the 6 year old bug you link has clearly been assessed as a bug affecting android (and not iPhone) and is exactly what you're describing, if I understood your issue correctly. Perhaps post a question in the bug report? Richard has done so previously to no avail...

Or maybe it's a bit cleaner to de-emphasize behaviours?

Behaviors can also be nested. The most complete representation is a vast spiderweb of connections, less instructive than a simplified model designed for learning core concepts. Agreed, which is why I didn't add anything, and the multiple behavior boxes seem annoying as well, but also seem necessary...

I do not have sufficient knowledge to correct the validity of the information in this diagram but if it is correct, I suggest using the color code from the previous diagrams (notably yellow for optional elements). And if it is correct, this diagram should appear on the official LC help, replacing t...

I'm sure many have used LC with something like this, but for a flat DB structure, or maybe smaller DBs with 1-2 levels of cross-"table" relationships. The main issue I imagine, is that you'd need to load the whole thing into memory. If your databases are large that will definitely be an issue. I dea...