Skip to content

Tag: Xojo API 2.0

ContainerControl: Composed User Interface Components

Xojo’s Library offers a good amount of UI controls ready to use: buttons, input text controls, lists, popup menus, progress bars, panels, labels, a control to play movies, etc. However, sometimes we need to display exactly the same combination of controls, using the same layout, in several windows of an app. What’s the best approach in these cases?

Comments closed

iOS User Authentication with Face ID

With the new UserAuthentication class available in Xojo 2021 Release 1, you can now easily ask an iOS user to authenticate themselves using Face ID, Touch ID or with their password/passcode. In an iOS project, add a UserAuthentication object to your screen and change its name to Authenticator.

Comments closed

MobileMoviePlayer

The MobileMoviePlayer is a relatively new iOS feature in the Xojo Programming language. To use MobileMoviePlayer start a new iOS project and drag the MoviePlayer control from the Library onto a Screen.

Comments closed

Creating your own ComboBox Subclass with Sorted Menu Items

The Xojo ComboBox desktop control is a powerful one. It combines the capabilities of a TextField with the PopupMenu. That means that you can choose from the available options in the associated menu or you can type another value in the ComboBox text field. What about getting the ComboBox to do things not included in the class?

Comments closed

#1 on the Xojo Roadmap: Android

We’re hard at work on Xojo’s upcoming Android support — it is our top priority. As we’ve discussed previously, you can see in the current versions of Xojo that the latest iOS controls now start with “Mobile” in their name. Although Android and iOS will start off as different project types, implementing the “Mobile” prefix is an important step to complete so you will see similar controls when Android support is available.

Comments closed

Use Multiple CPU Cores with Worker

A Worker provides a way for you to have code that runs on multiple CPU cores. A Worker achieves this by running its code in a Console app. One or more of these console apps are started based on your Worker settings. Since these run as Console apps, the OS treats them as separate processes and spreads them out amongst available CPU cores.

Comments closed