LiveCode Forums

OK, I think we're on the same page... just saying the same thing differently ;) That being said... how would you like to see that inset graph changed? the latest version seems fine to me, and not really saying anything different from what you say. I agree, the flow for behaviors is a bit complicate...

My comments about the message path are a paraphrase from the documentation: A before handler allows developers to produce behavior scripts which can handle messages sent to a control without having any effect on the message path, unlike front and back scripts. So, yes, the message does travel a slig...

Can you please elaborate on That side route should be “not in” but before/after still will get called. I'm not sure I understand this? I now realise the right side-arm ('Handled in object 1') is wrong and should be removed, not sure if that's what you mean? Yes the 'before' handler in the behaviour...

Let me reply with code. Consider the following code that will be in each of 3 buttons and the card: before mouseup put "before mouseup" && short name of me && short name of this me & lf after fld "Log" pass mouseup end mouseup on mouseup put "on mouseup" && short name of me && short name of this me ...

Hi Brian, What do you think of having this as an inset graph to accompany the main graph? Obviously open to corrections... 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...

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 con...

Take a look at my project here:
https://github.com/bwmilby/mobileDemo

You may just need to try setting the rect of the stack and not the height/width. That is how I changed stack size in the above project.

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. One other caution -...

I’ll need to go back and look at the code in SivaSiva. I guess that app locks the orientation much more so it isn’t noticed as much. Most of it locks to portrait or landscape. I only have an old Pixel to test Android and have not built for it in quite a while. The only rotation issue I recall is the...

Simplest way is to just use the resizeStack message to make any geometry changes. If rotation is locked on the device you should not get a resizeStack message.

I started a reply on my phone Sunday morning and lost it when I hit submit. I apologize for the delay in my response. Here is a much simpler example stack: https://github.com/bwmilby/mobileDemo/tree/master The third card is the one with the tree widget. The resizeStack handler is the one that has th...

Here are the key handlers from that project (trimmed slightly): command createScroller pName local tRect deleteMobileControl pName -- delete any existing if not isMobile() then exit CreateScroller end if put (the rect of control pName) into tRect mobileControlCreate "scroller", pName mobileControlSe...

It wasn’t slow for me, but the tree was much smaller than 100 keys. You can see it in a live app in the App Store if you download SivaSiva and go to the Stories module. Even though that project is in hiatus the code is all available.

I think I had this pretty much sorted out in SivaSiva. I have not looked at the code in over a year, but the stories module behavior script and the mobile controller behavior script are the two key places. I'll try to provide some more helpful code references this weekend. The key difference is that...

It is certainly possible to write a script that will export a stack into a script only form. Certain things would make the process more complex. If you count on object IDs being a certain value for example. Another issue is any binary objects (images…) - do you want to reference files or include the...