PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
  • Overview
  • Available project elements
  • Available controls
  • Databases
  • Modal windows
  • Loopers
  • Automatic scrollbars in the windows
  • Running the project code
  • Managing character strings
  • Managing directories
  • Changing the screen orientation
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
The method for developing applications for iPhone/iPad differs from the method for developing applications with WINDEV Mobile in the following areas:
Available project elements
The following project elements are available for iPhone/iPad development:
  • Windows. A window wizard is used to create specific windows for iOS.
  • Queries.
  • Classes.
  • Sets of procedures.
  • Window templates.
  • Control templates.
  • Versions 18 and later
    Reports and report templates.
    New in version 18
    Reports and report templates.
    Reports and report templates.
  • Versions 17 and later
    Internal windows.
    New in version 17
    Internal windows.
    Internal windows.
The following elements are not available for iPhone/iPad development:
  • Components.

Available controls

The following controls are available for the iPhone/iPad development:
Versions 20 and later
New in version 20
Notes:
  • No accented character should be used in the project name.
  • To insert images and icons into your iPhone/iPad applications, the image catalog proposes specific images. All you have to do is select the "iOS" theme during your search. Your interface will use the standard images available for the iPhone/iPad applications.
  • Versions 20 and later
    Managing images according to the DPI: The images can be bit-mapped or blurred according to the DPI of the device. You have the ability to use the automatic management of DPI. See Android/iOS: Providing an image per DPI for more details.
    New in version 20
    Managing images according to the DPI: The images can be bit-mapped or blurred according to the DPI of the device. You have the ability to use the automatic management of DPI. See Android/iOS: Providing an image per DPI for more details.
    Managing images according to the DPI: The images can be bit-mapped or blurred according to the DPI of the device. You have the ability to use the automatic management of DPI. See Android/iOS: Providing an image per DPI for more details.
Databases
The databases of applications for iPhone/iPad must be in HFSQL Classic or HFSQL Client/Server format.
The main Hxxx commands are available. The queries are also available.
For a database in HFSQL Client/Server format, the data files of the iPhone/iPad application can be shared with other applications (other than iPhone/iPad applications).
Notes:
  • No accented characters should be used in the names of HFSQL data files.
  • An automatic data modification can be performed while an application is updated. To apply the modifications performed in the analysis to the data files deployed on iPhone or iPad, all you have to do is use HModifyStructure (in the initialization code of the project for example).
Remark: From version 19, HFSQL is the new name of HyperFileSQL.
Modal windows
The modal widows are not supported by the iOS operating system. Open is not allowed.
The windows can be opened:
To pass a return value:
  • 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.
  • Versions 18 and later
    You can specify the return value via the ..ReturnedValue property of the child window, and retrieve this value via the event "Closing a child window of the window" of the parent window.
    New in version 18
    You can specify the return value via the ..ReturnedValue property of the child window, and retrieve this value via the event "Closing a child window of the window" of the parent window.
    You can specify the return value via the ..ReturnedValue property of the child window, and retrieve this value via the event "Closing a child window of the window" of the parent window.
Loopers
In the iPhone/iPad applications, the Looper controls can be in edit.
Note: The Looper controls can be used to replace the Table controls in an iPhone application. The Table controls are not used on the iPhone for the following reasons:
  • The interface of Table controls is not suitable.
  • Problem regarding the space in the windows: the columns and the column headers would not be displayed.
  • The row height would be too small to be handled with the fingers.
  • The Table controls are not used in the interface standard of this system.
Versions 20 and later
From version 20, Table controls are available in iPhone/iPad applications.
New in version 20
From version 20, Table controls are available in iPhone/iPad applications.
From version 20, Table controls are available in iPhone/iPad applications.
Automatic scrollbars in the windows
If the size of a window exceeds the size of the screen and if "Automatic scrollbars" is checked in the window description, a scrollbar is automatically added to the right of window. Its presence must be taken into account when designing the window in order for this scrollbar not to overlay the controls.
Running the project code
The maximum duration for running the project code must not exceed 10 seconds. Which means that if the code exceeds this duration, the application is not loaded.
Furthermore, if OpenChild is used in the project code in the middle of other code lines, all the lines are run first, then the window is opened.Furthermore, if OpenMobileWindow (or OpenChild) is run in the project code in the middle of other code lines, all the lines are run first, then the window is opened.
Managing character strings
When developing a project for iPhone/iPad, the iOS system is using character strings in Unicode format.
By default, in the following declaration:
MyString is string
The MyString variable is automatically considered as being a Unicode string.
To specify that a character string is in Ansi format, you must use the following declaration:
MyString is ANSI string
Managing directories
The management of directories in the iPhone/iPad applications presents these specific features:
  • By default, the current directory of an application corresponds to the "Documents" sub-directory that is automatically created in the setup directory of the application.
  • 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 root directory of the application.
For more details on the management of application directories, see Summary table: Managing directories according to the platform.
Changing the screen orientation
Three orientation modes are available for the windows ("Details" tab of window description):
  • Free: the window follows the orientation.
  • Locked in Portrait mode.
  • Locked in Landscape mode.
If the window follows the orientation, you must uncheck the option"Automatic Scrollbars" ( "Details" tab of the window description).
To detect the change in screen orientation, use the event "Change of orientation" in the windows.
Minimum version required
  • Version 17
Comments
Click [Add] to post a comment