LiveCode Forums

You can write the same code in about half the length in LC - but that code in Fluter is the entire app - no binary resources, no creating a stack, adding labels etc. Not entirely accurate though. When you create a new project there are a few different files that are generated. Any graphics and such...

Any iOS device with a notch will not work in upside down mode.

Probably a good reason to use ScriptTracker for binary stacks posted to GitHub. This would increase the number of livecodescript files posted there with very little work on the developer (I.e. no need to convert to SOS/behaviors).

I never actually tried 9 but got the Oracle version of 8.

I do a bit of editing in Atom. No need to manually copy/paste though. Take a look at ScriptTracker if you would like to edit your scripts from binary stacks in an external editor. It also allows easy tracking of script changes in a stack using Git.

If you modify the source to generate a nested array, then the tree view widget could display the data fairly efficiently. Another alternative is Trevor’s DataView Tree. He has an example that displays a folder hierarchy (GitHub.com/trevordevore/dataview_demo). Someone may have a nifty way to parse y...

Simple. Don’t try to use screenRect on mobile. Use the rect of this card instead.

You should not need to be using screenrect at all on mobile. Download SivaSiva to see a LiveCode app that is responsive to the screen size (most of the app).

All objects are place relative to the card, not the screen. The rect that you need to use is the rect of the card.

Try the following changes to your stack script: comment out the 2 lines where you set the stack size in preOpenStack and add the following handler: on resizeStack local tRect put the rect of this card into tRect put item 1 of tRect into gScreenRect1 put item 2 of tRect into gScreenRect2 put item 3 o...

I think that is just Android. The virtual hardware buttons are not included in the screenrect. Same thing on the Pixel that I use for development. This is also a key difference between iOS and Android. On iOS you can address the full screen (behind the “furniture”) but you can’t on Android. But, you...

What you are actually running up against is the fact that the profile manager library has not been updated to handle widgets. That is probably one reason that the UI for it was not included in the IDE update.

One thing that I think is being lost is that if "textChanged" was sent when the field was updated by script, then you could get yourself into a really bad recursion loop. One of the uses of the message is to clean up a field after user interaction which very well may end up making another change to ...

Another tidbit about the tree widget is that a feature has been added to facilitate manual sort. You can specify a number of characters to trim from the beginning of the key on display. This allows you to pre-pend a sort key before the display key. (i.e. 00-First key, 01-Second key, ... where 3 char...

One thing to check is to connect your phone and then unlock it. You may see a message about trusting the computer.

About the only thing you could do is to use the screen ratio instead of actual pixel size to determine if it is going to have that virtual button. My guess is that Apple is going to eventually remove the physical button from all phones but in doing so the aspect ratio will likely remain taller/wider...