![xojo properties xojo properties](https://blog.xojo.com/wp-content/uploads/2018/10/2018-10-11_12-31-29.png)
Added CNContactPickerViewControllerMBS class for iOS to pick contact.Added CalculateTOTPMBS function and CurrentUnixTimeMBS function to create Time-based one-time passwords.Added AVPlayerLooperMBS class to loop items playing in AVQueuePlayerMBS class.Added "MariaDB:" prefix for SQLDatabaseMBS class.Added UIDocumentPickerMBS class with a file open/export dialog for iOS.
Xojo properties windows#
Added 64-bit Windows ARM plugin support.Added MongoDB classes to connect to Mongo databases.To Paul Lefebvre for Xojo-gpio and Björn Eiríksson for his brilliant Einhugur Tech blog.Īnd of course to whoever stands behind the pigpio library. See (especially Joe’s post where he explains what is supposed to work in the current Xojo release, though not officially supported) Instead, you have to hardcode results and properties into shared or otherwise safe properties and use the shared pigpio external declares. In extensive tests and conversations with other developers, I have found the current solution to be stable as long as you do not access Xojo instances and instance properties and methods. Please note that the use of pigpio timers, interrupts and other callbacks is subject to discussion on the Xojo forums and not supported by Xojo officially. If you need to use Xojo methods that lock to an object, it is safe to store the interrupt parameters into Xojo properties. Please see the DemoButton class for an example. Therefore you must not use or create any Xojo objects, but it is safe to use external methods and datatypes. Instead, interrupt-driven controls feature a shared method that is exectued on the background thread. This is, if possible, complicated at least, because the events are returned on a background thread and it would be very difficult to get onto the virtual sensor instance. Yes, it would be the highest Xojo level of comfort to have events firing when the level of a sensor changes. You set the PWM dutycycle of a Pin by pigpio.AnalogValue(Pin) = value and get it by Dim value as Integer = pigpio.AnalogValue(Pin). Keep your method calls in try/catch causes therefore if you want to handle errors.Īs stated above, whereever a getter and a setter to a property exists, I have synthesized methods behaving like computed properties. To prepare this library better for the new Xojo framework, I fire exceptions when the result is below 0, adding the exception message according to pigpio‘s error list. Whereby pigpio returns you an integer for as good as method call, I have only done so if this return value needs to be remembered, like a handle.
![xojo properties xojo properties](https://www.monkeybreadsoftware.de/xojo/xdevmag/14.6-1.jpg)
Differences to pigpio original implementation Look into the description tags or consult the pigpio documentation at.
![xojo properties xojo properties](https://www.monkeybreadsoftware.net/DynaPDF3.jpg)
Xojo properties how to#
Look into the classes in the module that demonstrate how to use the library.Ī gpioWrite for example is pigpio.DigitalValue(GPIOPin) = True or False, while you can get the value via pigpio.DigitalValue(gpioPin).Īll public methods and properties are documented. Just change their scope and maybe unhide them. If you want to use it in a form closest to the original, you find the declare as external methods in the module. I tried to create virtual properties and convenience methods around the library.
![xojo properties xojo properties](https://www.mbsplugins.de/image/xojoos.jpg)
(Besides a lot of fairly untested pigpio declares): Please see the demo console app and the method descriptions. A Xojo library for pigpio features in Raspberry Pi projects