• Available project elements.
• Available controls.
• Databases.
• Application menus.
• Modal windows.
• Management of "Back" and "Home" buttons.
• Notification about the application inactivity.
• Operating mode of focus and selection.
• Automatic scrollbars in the windows.
• Using native Java code in an Android application.
• Using native Kotlin code in an Android application.
• Management of directories.
• Changing the screen orientation.
• Miscellaneous.
• Threads.
• Indirection operators.
• Use of native Android fonts.
• Management of ADB logs.
• PDF print jobs.
• API Level (TargetSdkVersion).
• Android 10: New behavior.
• Android 11: New behavior.

• Windows.
• Queries.
  Remark: in a query with parameters, all the parameters are mandatory.
• Classes.
• Sets of procedures.
• Window templates.

• External components.
  Remark: Internal components are available for Android development. However, if the internal component includes an analysis, this analysis will be ignored during the execution.
• Reports and report templates.

Available controls

• Button control
• Combo Box control
  Remark: A negative or null value cannot be assigned to a Combo Box control. If the Combo Box control is not empty, an element has to be selected. An error will occur if a negative or null value is assigned to a Combo Box control.
• Image control
• Check Box control
• Static control
• List Box control
• Tab control
• Edit control
• Radio Button control
• Looper control

• Some style properties ("Style" tab of control description windows), although available in edit mode, are not supported by Android applications.
• You can use a gradient for the background color of the control borders.

• HFSQL (Classic and Client/Server),
• SQLite.
  WINDEV Mobile includes a Native Connector for SLQLite for Android. The main Hxxx commands are available.

• Memos with HFSQL: The mode used for strings at runtime (UNICODE or ANSI) defined in the project configuration determines the character set used to store strings. By default, ANSI strings assigned to HFSQL memo items are encoded in UTF-8. ChangeCharset can be used to change the character encoding
• SQLite database: If your Android project shares its analysis with another (non-Android) project, HChangeConnection can be used to associate the data files of the application with an SQLite connection. For more details, see Android application: Using and sharing data.
• Memos with SQLite: Storing information in memo format is recommended for the data whose size is less than 1 MB. We advise you to directly save the data in external file format on the internal or external memory of the phone and to store the access path to this data in the database.
• You also have the ability to access an external database (Oracle, SQL Server, ...) via a Webservice. For more details, see Accessing a database via a Webservice.

• via the Action Bar control. This solution is recommended.
• in menu format (not recommended).

• In edit, the menus of the Android windows are presented like simple drop-down menus.
• At runtime, these menus will be displayed differently according to the number of options:
  • If the menu contains less than 6 options, it is displayed like large buttons at the bottom of the screen.
  • If the menu contains more than 6 options, the first 5 options are displayed like large buttons and a sixth automatic button ("Plus") allows the user to see the rest of menu like a drop-down menu.
• The menus of Android applications support a single level of submenus. Beyond this limit, a fatal error occurs when running the application.

Context menus

• In edit mode, they are presented like Windows drop-down menus but they adopt the appearance of Android menus at runtime.
• They are also limited to a single submenu level.
• On the devices without "right click" (phones for example), the popup menus are displayed after a "long press" on the control to which they are associated.

• by the OpenChild function,
• by the OpenSister function,
• by the OpenMobileWindow function.

• When it is closed, a child or sibling window can call a local procedure of the window that opened it in order to pass a return value to it. A return value can also be returned via a global variable.
• You can specify the return value via the ReturnedValue property of the child window and retrieve this value via the "Close a child window of the window" event of the parent window.

Back button

Home button

• The focus can only be moved with a mouse, a trackball or a similar device.
• When the focus is moved, the entry and exit event of the controls are run.
• The clickable but non-editable controls (buttons, list boxes, etc.) behave like the controls in interruption. They do not take focus when they receive a click.
• The "Select a row" event in List Box and Looper controls is run only when the row is selected with a click.
• The "Select a row" event in List Box and Looper controls is not run when the row (with the focus) changes.

• By default, the current directory of an application corresponds to the "files" subdirectory that is automatically created at the root of the application setup directory.
• The relative paths handled by the application are relative to this directory.
• The full path of current directory is returned by fCurrentDir. By default, you have the ability to read and write in this directory.
• The current directory can be modified by fCurrentDir.
• The runtime directory (returned by fExeDir) corresponds to the application installation directory. By default, the applications are always installed in the /data/data/<package name>.<application name> directory.
• In Android, the file system is read-only on the device and on the emulator. An application can only write to its installation directory or one of its subdirectories, as well as to the external memory (SDCard).
• The "databases" directory is also automatically created at the root of application installation directory to store the SQLite databases handled by the application (unless a specific path was specified during the connection). The path of the "databases" directory is returned by fDataDir.
• To have a storage location common to several applications, use the external memory (SDCard for example). The path of a directory for storing files in the external storage space is returned by SysDirExternalStorage.
• When connecting a device to the PC using the "mass storage" or "disk drive" mode, the SD Card is automatically unmounted from the device and is no longer accessible from it. All running applications installed on the SD Card are killed. While the SD Card is unmounted, you will not be able to:
  • start the applications installed on the SD Card.
  • access the SDCard from the applications run on the phone.

• Summary table: Managing directories according to the platform.
• Storing files in Android.

• In Android, for security reasons, the "Home" and "End of call" keys cannot be used as shortcuts.
• To use the "Material Design" theme, in the "General" tab of the Android configuration description, check "Apply Material design theme to native controls and to Info/Error/Dialog windows".
• Managing images according to the DPI: The images can be bit-mapped or blurred according to the DPI of the device. You can use the automatic DPI management. For more details, see Android/iOS: Providing an image per DPI.
• CSS styles in SVG images are not supported on Android.

Debugging deployed applications via the ADB logs

• Messages of Trace ("Info" level).
• Messages of dbgStandardOutput ("Debug" level).
• Messages of asserts (dbgAssert, dbgCheckxxx, dbgError) ("Assert" level).
• Messages of fatal and non-fatal errors ("Error" level).

• in the Android Control Center ("Logcat" tab): on the "Tools" tab, in the "Mobile tools" group, click "CCAndroid").
• on each phone. Specific software are used to process and view the content of this file.
• via the "Monitor" tool available in the Android SDK. In this case, you have the ability to view (in the "Log cat" tab) the ADB logs of all applications found on the device connected to the PC (the "USB debug" mode must be enabled on the device. For more details, see Preparing the phone to test an Android application).