LiveCode Forums

At the moment, yes it is just a method to deploy FileMaker projects. There are no plans to turn it into a converter - they way it works is using a virtual machine / bytecode style model, rather than producing readable LiveCode. In the future it may be possible to augment deployed FM projects with Li...

Have a look at revIDECreateTransientTextField and associated handlers in the IDE - this is how we do it with the navigation bar property inspector.

It doesn't have to be a whole new widget, but yes, within the widget you need specific logic for returning a value - see the 'currently popped up' syntax in the dictionary, or the code in the icon picker.

In general widgets require specific coding to handle the case when they are popped up by some other script

There is no such widget - I think the docs were intended to be illustrative rather than literal there. It would be better to replace with a working example though, so it could be changed to "com.livecode.widget.iconpicker" with selectedIcon instead of currentColor. If you are asking because you actu...

I'm still confused as to the specific issue here - if the handler shows up in the default handler list (and nothing else) then that is the expected behavior - we did away with default scripts actually populating the script, they merely define a list of handlers for the default handler list. If I loa...

No, it should happen automatically. However, I'm wondering if there may be a docs issue here - we changed default scripts so that the handlers specified show up in the left hand side, rather than the script actually being automatically filled in - does your default script consist of (a) handler(s) a...

support should be lowercase, although possibly that isn't the issue if you're on an os with a case insensitive file system. Your default script stack needs to be named "your.widget.identifier.__DefaultScript", eg: script "com.livecode.widget.navbar.__DefaultScript" Other than that, the only reason I...

Yes, the cross platform button example is how we would recommend structuring such an extension: https://github.com/livecode/livecode/pull/6266 However it does potentially over-complicate things it if the extension is very simple, and you can do as Trevor suggests (in fact the first LiveCode widget t...

Hi Max, I added an overview of the canvas API with examples in the Extending LiveCode document in the 9.0 GM release: https://github.com/livecode/livecode-ide/blob/develop/Documentation/guides/Extending%20LiveCode.md#canvas-api Please give that a read and let me know what we can do to improve it. Th...

Yes, you could change the template manifest - it's at LiveCode Community 9.0.0.app/Contents/Tools/Runtime/Android/Manifest.xml for example on Mac

In the IDE you can do revIDEExtensions() to get an array with all the metdata. You can cut that down with parameters, eg revIDEExtensions("library") or revIDEExtensions("widget", "installed"). For individual extension properties, use revIDEExtensionProperty(<kind>, <propName>) where propName is vari...

The extensions course contains code for a rotated text widget here (click the downloads icon on the right)

Hmm, that suggests something is being over-released, which means it is likely being marked as retained when it shouldn't be... I'm sure it will be something simple!

Your code and everything looks correct, with the exception of __safe foreign handler JNI_SayHello() returns JString binds to "java:com.example.uhfreader816ubt.HelloAndroid>sayHelloAndroid()Ljava/lang/String;" As the sayHelloAndroid method is static, your binding string should be java:com.example.uhf...