Windev Mobile 17 Free Download

fullpacicloud.netlify.com › Windev Mobile 17 Free Download ▀ ▀

May 11, 2012 - You must own a registered English or International version of WINDEV Mobile 17, before downloading the module proposed on this page. WINDEV Mobile 17 US is available. How do I install this. Please retry later. If you still can't download a copy after a few attempts, contact our Free Technical Support. Jul 16, 2016 - Download WinDev Mobile for free. The 19.0 version of WinDev Mobile is provided as a free download on our software library. WDMobileExpress.exe, WD9Mobile.exe, WD19Mobile.exe, WD18Mobile.exe, WD17Mobile.exe, WD16Mobile.exe, WD15Mobile.exe, WD14Mobile.exe, WD12Mobile.exe,.

Windev Crack
Windev Developers
Windev

WINDEV Mobile 20 Free Download Latest Version for Windows. It is full offline installer standalone setup of WINDEV Mobile 20 Free Download for 32/64. WINDEV Mobile 20 Overview WINDEV Mobile 20 is an application which can be used for developing apps for the Smartphones, Tablets and Industrial devices. With this application you can develop native applications quickly and you can distribute your applications freely. You can also download. The development environment is integrated, powerful, intuitive and it is adopted to the specificities of mobile devices.

This application comes with all the tools which are needed for managing the entire life cycle of applications like Windows generator, setup generator, Windows generator and 5GL etc. It offers the usual development features but also loads of feature specific to the use of the mobile devices like SMS reading, accelerometer management, GPS positioning, bar codes and compass management. There is a 5 th generation language which will let you develop quicker than the traditional language. The powerful functions will make the code easier to write and read by simplifying both the development and the maintenance. The compatibility of WINDEV and WINDEV Mobile is amazing.

The database programming is identical and you can also share and reuse most of the codes, classes, queries and controls. You can also download. Features of WINDEV Mobile 20 Below are some noticeable features which you’ll experience after WINDEV Mobile 20 free download.

Handy application for developing apps for the Smartphones, Tablets and Industrial devices. Can develop and distribute native applications quickly. Got an integrated, powerful and intuitive environment adopted to the specificities of mobile devices. Comes with all the tools which are needed for managing entire life cycle of applications like Windows generator, setup generator and 5GL etc. Offers SMS reading, accelerometer management, GPS positioning, bar codes and compass management features.

Supports 5th generation language which will let you develop quicker than the traditional language,. The compatibility of WINDEV and WINDEV Mobile is amazing. The database programming is identical and you can also share and reuse most of the codes, classes, queries and controls. WINDEV Mobile 20 Technical Setup Details. Software Full Name: WINDEV Mobile 20. Setup File Name: WINDEVMobile20Build66r.zip. Full Setup Size: 3.3 GB.

Setup Type: Offline Installer / Full Standalone Setup. Compatibility Architecture: 32 Bit (x86) / 64 Bit (x64). Latest Version Release Added On: 24th Dec 2017. Developers: System Requirements For WINDEV Mobile 20 Before you start WINDEV Mobile 20 free download, make sure your PC meets minimum system requirements. Operating System: Windows XP/Vista/7/8/8.1/10. Memory (RAM): 1 GB of RAM required.

Hard Disk Space: 3 GB of free space required. Processor: Intel Dual Core processor or later.

WINDEV Mobile 20 Free Download Click on below button to start WINDEV Mobile 20 Free Download. This is complete offline installer and standalone setup for WINDEV Mobile 20.

This would be compatible with both 32 bit and 64 bit windows.

Versions 21 and later The Android SDK and Gradle are required to create the Android executable. You can:.

Download and install these tools automatically. In this case, WINDEV Mobile downloads and installs all the necessary tools with the requested options. Only an Internet connection is required.

Use the tools automatically installed. This option is available if the tools have been downloaded and installed during a previous generation. Use the tools already installed on your computer. In this case, all you have to do is specify the setup paths of Gradle and Android SDK. See for more details. New in version 21 The Android SDK and Gradle are required to create the Android executable. You can:.

Windev Crack

This option is available if the tools have been downloaded and installed during a previous generation. Use the tools already installed on your computer. In this case, all you have to do is specify the setup paths of Gradle and Android SDK. See for more details. The Android SDK and Gradle are required to create the Android executable. You can:.

Download and install these tools automatically. In this case, WINDEV Mobile downloads and installs all the necessary tools with the requested options. Only an Internet connection is required.

Specify the application name and the package. The application name is the name that will be displayed below the application icon. New in version 18 For the multilingual applications, this name can be entered in several languages.

During the setup, the name of the application will be chosen according to the language settings specified for the device. If the application name is not available in the device language, the name defined for the default language of project will be used. For the multilingual applications, this name can be entered in several languages. During the setup, the name of the application will be chosen according to the language settings specified for the device. If the application name is not available in the device language, the name defined for the default language of project will be used. The package is used to identify the application. By convention, it contains the company name (or its Internet domain name in reversed order) followed by the application name.

The application name corresponds to the name in the default language of project. Choose (if necessary) an icon for the application (image in PNG format). This icon is used to make the application more visible in the menu of applications.

The default icon will be used if no icon is selected. New in version 18 Specify whether the application must display (or not) a splash screen at startup. The splash screen is used to make the user wait while running the initialization code of the project. See for more details. Specify whether the application must display (or not) a splash screen at startup. The splash screen is used to make the user wait while running the initialization code of the project. See for more details.

Enter the general information about the application: the company name, the copyright and the application description. New in version 18 Specify whether the application must be automatically launched when starting the device system. Note: is used to find out the start mode of Android application.

Specify whether the application must be automatically launched when starting the device system. Note: is used to find out the start mode of Android application. Go to the next step. Specify the version number of generated application. Two formats are available for the version numbers:. Standard format.

This format is the standard format supported by Windows. This format corresponds to a set of 4 numbers separated by dots.

The first group of 4 digits corresponds to the number of major changes performed in the application. The second group of 4 digits corresponds to the number of minor changes performed in the application. The third group of 4 digits corresponds to the generation number. We advise you to automatically increment this number at each generation. This increment operation is automatically performed if 'Automatically increment the version at each generation' is checked. The last group of 4 digits corresponds to the number of reviews (branches in the SCM for example).

We advise you to automatically increment this number at each generation. This increment operation is automatically performed if 'Automatically increment the version at each generation' is checked. Format for compatibility. This format was used until version 12 for the WINDEV applications. Note: All the characters (digits and letters) are allowed. For example: '1.01A'. We advise you to:.

use a different version number whenever the executable program is created. Indeed, when installing an update, this version number is used to check whether the update is mandatory or not. automatically increment the last characters (digit or letter) of the version number whenever the executable program is created (check 'Automatically increment the version at each generation'). For example: - the version number '1.01A' will become '1.01B'. the version number 'A15Z' will become 'A16A'. Go to the next step. The signature of the application is mandatory for a setup on an Android device.

It can be done according to three different methods:. Using a couple of public/private keys bought toward a trusted authority: this solution is recommended if the application must be distributed in a business way. It guarantees that the application author can be identified. Using a couple of auto-signed public/private keys: this solution can be used if the application is distributed inside a company for example. It avoids going through the trusted authority (whose services are charged for in most cases). Using a generic signature: this solution can be used when developing the application. Select the permissions required by the application to operate.

Each application must indicate to the Android operating system the services to which it must access in order to operate (access to Internet, access to the camera, etc.). WINDEV Mobile automatically adds the necessary permissions according to the statements used in the application.

Note: If procedures written in native Java have been used, the corresponding permissions must be specified. New in version 17 If your application is available on Google Play, you have the ability to propose your application only for the devices supporting the features used by your application. For example, if your application is using the inertial scroll, it will only be proposed for the devices supporting this feature. You can choose to add or remove specific features. If your application is available on Google Play, you have the ability to propose your application only for the devices supporting the features used by your application. For example, if your application is using the inertial scroll, it will only be proposed for the devices supporting this feature.

You can choose to add or remove specific features. Versions 16 and later Specify whether files and libraries must be included in the Android application. You have the ability to include:. specific resources. specific Java archives. Then, these files can be:. used directly (files to read for example: sound files, image files.).

extracted by (files to modify by the application for example). If an image is included in the Android application, it can be directly assigned to a control by specifying its name. For example, IMGImage = image1.

New in version 16 Specify whether files and libraries must be included in the Android application. You have the ability to include:. specific resources. specific Java archives. Then, these files can be:.

used directly (files to read for example: sound files, image files.). extracted by (files to modify by the application for example). If an image is included in the Android application, it can be directly assigned to a control by specifying its name. For example, IMGImage = image1 Specify whether files and libraries must be included in the Android application. You have the ability to include:. specific resources.

specific Java archives. Then, these files can be:.

The generation is using the Android SDK. It may be useful to specify its location (in most cases, this location was specified when creating the first Android project).

In the 'Platform' combo box, choose the version of Android for which the application must be compiled. You also have the ability to customize the compilation commands. Notes:. WINDEV Mobile can generate applications compatible with the versions 1.5 (and later) of Android. See the documentation about the Android SDK for more details. Versions 21 and later The Android SDK and Gradle are required to create the Android executable.

You can:. Download and install these tools automatically. In this case, WINDEV Mobile downloads and installs all the necessary tools with the requested options. Only an Internet connection is required. This method is recommended. Caution: The first download can be quite long.

Use the tools automatically installed. This option is available if the tools have been downloaded and installed during a previous generation. Use the tools already installed on your computer.

In this case, all you have to do is specify the setup paths of Gradle and Android SDK. See for more details. New in version 21 The Android SDK and Gradle are required to create the Android executable. You can:.

Download and install these tools automatically. In this case, WINDEV Mobile downloads and installs all the necessary tools with the requested options. Only an Internet connection is required. This method is recommended. Caution: The first download can be quite long. Use the tools automatically installed. This option is available if the tools have been downloaded and installed during a previous generation.

Use the tools already installed on your computer. In this case, all you have to do is specify the setup paths of Gradle and Android SDK. See for more details.

The Android SDK and Gradle are required to create the Android executable. You can:.

Caution: The first download can be quite long. Use the tools automatically installed.

This option is available if the tools have been downloaded and installed during a previous generation. Use the tools already installed on your computer. In this case, all you have to do is specify the setup paths of Gradle and Android SDK. See for more details. New in version 18 For the multilingual applications, this name can be entered in several languages.

For the multilingual applications, this name can be entered in several languages. During the setup, the name of the application will be chosen according to the language settings specified for the device. If the application name is not available in the device language, the name defined for the default language of project will be used. The package is used to identify the application. By convention, it contains the company name (or its Internet domain name in reversed order) followed by the application name. The application name corresponds to the name in the default language of project. Choose (if necessary) an icon for the application (image in PNG format).

This icon is used to make the application more visible in the menu of applications. The default icon will be used if no icon is selected. A preview of the icon is displayed. The arrow button is used to select different icons according to the density of the screen (low density, medium density, high density and very high density). The user can:. Click the 'Error report' link to see the error displayed. Check the box 'Send the error report by email'.

In this case:. if the email address was specified, the box will be checked by default and the user will receive the error report in his messaging with the 'Sender' and 'Recipient' parameters filled. if the email address was not specified, the user will receive the error report in his messaging and it will have to fill the recipient address.

Note: To identify the problems encountered by the end user, you also have the ability to use the ADB logs. See for more details. The user can:.

if the email address was not specified, the user will receive the error report in his messaging and it will have to fill the recipient address. Note: To identify the problems encountered by the end user, you also have the ability to use the ADB logs. See for more details. Specify the email address that will be used by default to send the error report during a fatal error. A specific window is displayed when a fatal error occurs in the application. The user can:.

Click the 'Error report' link to see the error displayed. Check the box 'Send the error report by email'. In this case:. if the email address was specified, the box will be checked by default and the user will receive the error report in his messaging with the 'Sender' and 'Recipient' parameters filled. if the email address was not specified, the user will receive the error report in his messaging and it will have to fill the recipient address. Note: To identify the problems encountered by the end user, you also have the ability to use the ADB logs. See for more details.

Go to the next step. New in version 18 Specify whether the application must display (or not) a splash screen at startup. The splash screen is used to make the user wait while running the initialization code of the project. See for more details.

Specify whether the application must display (or not) a splash screen at startup. The splash screen is used to make the user wait while running the initialization code of the project. See for more details. Enter the general information about the application: the company name, the copyright and the application description. New in version 22 Specify whether the maximized application windows can be resized (multi-Window). This option is taken into account from Android 7. If this option is enabled, the windows can be displayed in different modes (1/3, 1/2 or 2/3).

Specify whether the maximized application windows can be resized (multi-Window). This option is taken into account from Android 7.

If this option is enabled, the windows can be displayed in different modes (1/3, 1/2 or 2/3). Go to the next step. Specify the version number of generated application. Two formats are available for the version numbers:. Standard format. This format is the standard format supported by Windows. This format corresponds to a set of 4 numbers separated by dots.

This format was used until version 12 for the WINDEV applications. Note: All the characters (digits and letters) are allowed. For example: '1.01A'. We advise you to:. use a different version number whenever the executable program is created. Indeed, when installing an update, this version number is used to check whether the update is mandatory or not.

automatically increment the last characters (digit or letter) of the version number whenever the executable program is created (check 'Automatically increment the version at each generation'). For example: - the version number '1.01A' will become '1.01B'.

the version number 'A15Z' will become 'A16A'. Go to the next step.

The signature of the application is mandatory for a setup on an Android device. It can be done according to three different methods:. Using a couple of public/private keys bought toward a trusted authority: this solution is recommended if the application must be distributed in a business way.

It guarantees that the application author can be identified. Using a couple of auto-signed public/private keys: this solution can be used if the application is distributed inside a company for example. It avoids going through the trusted authority (whose services are charged for in most cases).

Using a generic signature: this solution can be used when developing the application. An application signed with a generic key cannot be published. Its use is limited to tests in 'Go' mode on the same development computer. Go to the next step. Specify whether files must be included in the Android application. You have the ability to include:. specific resources: images.

HFSQL data files used by the application. New in version 22 Note: The 'Asset' directory is also proposed. Note: The 'Asset' directory is also proposed. If the 'Write' option is checked:. the file extraction is automatically performed when starting the application (before running the initialization code of the project). you have the ability to specify an extraction directory.

By default, the data files are extracted into the directory of the database Caution: if the files in 'Write' mode already exist on the mobile during the setup, they will not be re-extracted from the archive. Go to the next step.

Specify whether libraries must be included in the Android application. You have the ability to include:. the HFSQL library.

This library is required if your application is using HFSQL data files. specific Java libraries. Specify whether libraries must be included in the Android application.

You have the ability to include:. specific Java libraries (.jar or.aar files). native libraries (SO files).

the HFSQL library. This library is required if your application is using HFSQL data files. Go to the next step. New in version 21 The wizard proposes to include Maven libraries in the executable. Go to the next step. The wizard proposes to include Maven libraries in the executable. Go to the next step.

Select the permissions required by the application to operate. Each application must indicate to the Android operating system the services to which it must access in order to operate (access to Internet, access to the camera, etc.). WINDEV Mobile automatically adds the necessary permissions according to the statements used in the application. Notes:. If procedures written in native Java have been used, the corresponding permissions must be specified.

New in version 22 From Android version 6, the authorization request is performed during the first use of the feature (beforehand, all the requests were grouped during the setup). From Android version 6, the authorization request is performed during the first use of the feature (beforehand, all the requests were grouped during the setup). Go to the next step. If your application is available on Google Play, you have the ability to propose your application only for the devices supporting the features used by your application. For example, if your application is using the inertial scroll, it will only be proposed for the devices supporting this feature. You can choose to add or remove specific features.

Windev Developers

Go to the next step. Specify the. If your application is using a Calendar control, a tab with swipe or an internal window with swipe, you must install the 'Android Support Library V4' extension. The Android application cannot be generated if this extension is not installed in the Android SDK. The procedure for installing this extension is available from:. If your application is using a Map control, fill the parameters specific to this type of control.

See for more details. If your application is using an Ad control, fill the parameters specific to this type of control. See for more details. New in version 22 use the Google Firebase platform (recommended): you must specify the configuration file downloaded from the Firebase configuration site. See for more details. Use the Google Firebase platform (recommended): you must specify the configuration file downloaded from the Firebase configuration site. See for more details.

use the Google Cloud Messaging platform: you must specify the Google API project numper. See for more details. Caution: the GCM platform is kept for compatibility with the existing projects. This platform is no longer supported by Google for the new projects. To use a splash screen, select 'Splash screen' in the wizard and click the 'Options' button to configure the information displayed:. The application name: #APPNAME# is used by default and it corresponds to the name of the application specified at the beginning of the generation wizard. This name can be modified.

The application version: By default, #VERSION# is using the version number specified in the generation wizard. This number can be modified. The load message: This message will be displayed on the splash screen. Used in the initialization process of the project allows you to modify this message dynamically. The application logo: This logo will be displayed below the name of the application.

An animation can be displayed while loading the application. The background image used in portrait mode and in landscape mode. A default image will be used if this image is not specified. If a start image is specified, you have the ability to indicate a specific image according to the resolution of the device used. To use a splash screen, select 'Splash screen' in the wizard and click the 'Options' button to configure the information displayed:. The application name: #APPNAME# is used by default and it corresponds to the name of the application specified at the beginning of the generation wizard.

This name can be modified. The application version: By default, #VERSION# is using the version number specified in the generation wizard. This number can be modified. The load message: This message will be displayed on the splash screen. Used in the initialization process of the project allows you to modify this message dynamically.

The application logo: This logo will be displayed below the name of the application. An animation can be displayed while loading the application. The background image used in portrait mode and in landscape mode.

A default image will be used if this image is not specified. If a start image is specified, you have the ability to indicate a specific image according to the resolution of the device used. To use a splash screen, select 'Splash screen' in the wizard and click the 'Options' button to configure the information displayed:. The application name: #APPNAME# is used by default and it corresponds to the name of the application specified at the beginning of the generation wizard. This name can be modified. The application version: By default, #VERSION# is using the version number specified in the generation wizard. This number can be modified.

The load message: This message will be displayed on the splash screen. Used in the initialization process of the project allows you to modify this message dynamically.

A default image will be used if this image is not specified. If a start image is specified, you have the ability to indicate a specific image according to the resolution of the device used. Versions 16 and later Setup location: The possible options are as follows:. Internal memory: The application will be installed in the internal memory of the device and it cannot be installed in the external memory (SD card for example).

The application will not be installed if the internal memory of the device is full. Internal memory movable to the SD card: The application will be installed in the internal memory of the device but it can be moved by the user into the external memory from the application for managing the applications (accessible from the menu of parameters of the device). If the internal memory of the device is full during the setup, the application will be installed in the external memory. SD Card movable to the internal memory: The application will be installed in the external memory of the device but it can be moved by the user into the internal memory from the application for managing the applications (accessible from the menu of parameters of the device). If the external memory of the device is full or not accessible during the setup, the application will be installed in the internal memory.

New in version 16 Setup location: The possible options are as follows:. Internal memory: The application will be installed in the internal memory of the device and it cannot be installed in the external memory (SD card for example). The application will not be installed if the internal memory of the device is full. Internal memory movable to the SD card: The application will be installed in the internal memory of the device but it can be moved by the user into the external memory from the application for managing the applications (accessible from the menu of parameters of the device). If the internal memory of the device is full during the setup, the application will be installed in the external memory. SD Card movable to the internal memory: The application will be installed in the external memory of the device but it can be moved by the user into the internal memory from the application for managing the applications (accessible from the menu of parameters of the device). If the external memory of the device is full or not accessible during the setup, the application will be installed in the internal memory.

Setup location: The possible options are as follows:. Internal memory: The application will be installed in the internal memory of the device and it cannot be installed in the external memory (SD card for example). The application will not be installed if the internal memory of the device is full. Internal memory movable to the SD card: The application will be installed in the internal memory of the device but it can be moved by the user into the external memory from the application for managing the applications (accessible from the menu of parameters of the device). If the internal memory of the device is full during the setup, the application will be installed in the external memory. SD Card movable to the internal memory: The application will be installed in the external memory of the device but it can be moved by the user into the internal memory from the application for managing the applications (accessible from the menu of parameters of the device). If the external memory of the device is full or not accessible during the setup, the application will be installed in the internal memory.

Versions 16 and later Consequences of installing an application in the external memory:. Only the APK file of the application is installed in the external memory. The application data (databases, external files, etc.) are still stored in the internal memory, at the same location as if the application was installed in the internal memory (/data/data//). The APK file installed on the external memory is encrypted with a key allowing it to operate with the device that installed it only. Therefore, an application installed on the SD Card operates for a single device. Installing an application on the external memory does not impact the performances of the application. If the user connects his device to the PC in 'mass storage' mode (or in 'disk drive' mode), the SD Card is automatically dismantled from the device and it is no longer accessible from this one.

All the applications installed on the SD Card and currently operating are killed. The applications installed on the SD Card will not operate as long as the SD Card is dismantled. New in version 16 Consequences of installing an application in the external memory:. Only the APK file of the application is installed in the external memory. The application data (databases, external files, etc.) are still stored in the internal memory, at the same location as if the application was installed in the internal memory (/data/data//).

The APK file installed on the external memory is encrypted with a key allowing it to operate with the device that installed it only. Therefore, an application installed on the SD Card operates for a single device. Installing an application on the external memory does not impact the performances of the application. If the user connects his device to the PC in 'mass storage' mode (or in 'disk drive' mode), the SD Card is automatically dismantled from the device and it is no longer accessible from this one. All the applications installed on the SD Card and currently operating are killed.

The applications installed on the SD Card will not operate as long as the SD Card is dismantled. Consequences of installing an application in the external memory:. Only the APK file of the application is installed in the external memory. The application data (databases, external files, etc.) are still stored in the internal memory, at the same location as if the application was installed in the internal memory (/data/data//). The APK file installed on the external memory is encrypted with a key allowing it to operate with the device that installed it only. Therefore, an application installed on the SD Card operates for a single device. Installing an application on the external memory does not impact the performances of the application.

If the user connects his device to the PC in 'mass storage' mode (or in 'disk drive' mode), the SD Card is automatically dismantled from the device and it is no longer accessible from this one. All the applications installed on the SD Card and currently operating are killed. The applications installed on the SD Card will not operate as long as the SD Card is dismantled. New in version 18 Customizing the manifest. The manifest generated for the Android application can be edited. You have the ability to add, modify, delete nodes or attributes. Caution: Modifying the manifest may trigger compilation errors or failures during the execution on the device.

Windev

Customizing the manifest. The manifest generated for the Android application can be edited. You have the ability to add, modify, delete nodes or attributes. Caution: Modifying the manifest may trigger compilation errors or failures during the execution on the device. The configuration parameters are as follows:. Android SDK: The generation is using the Android SDK.

You may have to specify:. its location (in most cases, this location was specified when creating the first Android project). the version used to compile the application. the minimum version required to run the application.

WINDEV Mobile can generate applications compatible with Android version 1.6 (and later). Note: If your application is using features not supported by the selected minimum version, a specific icon is displayed on the right of the minimum version. An information message allows you to see the details of the features that will not be supported if this minimum version is kept.

You may have to specify:. its location (in most cases, this location was specified when creating the first Android project). the minimum version required to run the application. WINDEV Mobile can generate applications compatible with the versions 1.6 (and later) of Android. Note: If your application is using features not supported by the selected minimum version, a specific icon is displayed on the right of the minimum version. An information message allows you to see the details of the features that will not be supported if this minimum version is kept. Setup location: The possible options are as follows:.

Internal memory: The application will be installed in the internal memory of the device and it cannot be installed in the external memory (SD card for example). The application will not be installed if the internal memory of the device is full.

Internal memory movable to the SD card: The application will be installed in the internal memory of the device but it can be moved by the user into the external memory from the application for managing the applications (accessible from the menu of parameters of the device). If the internal memory of the device is full during the setup, the application will be installed in the external memory. SD Card movable to the internal memory: The application will be installed in the external memory of the device but it can be moved by the user into the internal memory from the application for managing the applications (accessible from the menu of parameters of the device). If the external memory of the device is full or not accessible during the setup, the application will be installed in the internal memory. Consequences of installing an application in the external memory:. Only the APK file of the application is installed in the external memory. The application data (databases, external files, etc.) are still stored in the internal memory, at the same location as if the application was installed in the internal memory (/data/data//).

The applications installed on the SD Card will not operate as long as the SD Card is dismantled. New in version 19 SHA1 print of the certificate used to sign the application: To modify this print, all you have to do is modify the certificate used. SHA1 print of the certificate used to sign the application: To modify this print, all you have to do is modify the certificate used.

Customizing the manifest. The manifest generated for the Android application can be edited. You have the ability to add, modify, delete nodes or attributes. Caution: Modifying the manifest may trigger compilation errors or failures during the execution on the device. New in version 21 Ignore the HTTPS errors: This option is checked by default and it is available for the applications created with a version earlier than WINDEV Mobile 21 and using the HTTP functions or the Webservices.

Caution: If you uncheck this option, it will not be redisplayed. To keep the operating mode of the application, you will have to use the 'HTTTP.IgnoreError = 0' statement in the code. In order to ignore the errors. Ignore the HTTPS errors: This option is checked by default and it is available for the applications created with a version earlier than WINDEV Mobile 21 and using the HTTP functions or the Webservices. Caution: If you uncheck this option, it will not be redisplayed. To keep the operating mode of the application, you will have to use the 'HTTTP.IgnoreError = 0' statement in the code.

In order to ignore the errors.