|
|
|
|
|
|
|
|
|
|
- Overview
- Why use the UI audit?
- How to?
- Implementing the UI audit and resolving issues
- Enabling or disabling UI audits for all projects
- Examples of detected problems
UI audit: Detect obsolete technologies
Projects are often several years old: a common occurrence. Projects often include features that date from the time the project was created. Some of these features are now outdated or have been replaced by better, more secure features.
Likewise, some options available by default in a previous version have become useless or inefficient. Sometimes, it is necessary to enable more modern options. Starting with version 27, WINDEV, WEBDEV and WINDEV Mobile highlight outdated features and suggest using the new features available. By following the recommendations of the UI audit and using new features in your projects: - You improve the performance of the editor:
The use of old technology fields can have an impact on the performance of your editors, slowing down their execution, generations, template updates, etc.
It is therefore a good idea to replace these old features with up-to-date alternatives. - You improve performance at runtime:
Old features slow down execution.
A simple way to increase the speed of your applications is to replace these outdated features. - You reduce page size and memory consumption:
In WEBDEV in particular, using controls with outdated features or parameters can result in larger and more memory-intensive pages.
Updating your controls will significantly optimize size and memory consumption!
Implementing the UI audit and resolving issues By default, the UI audit is enabled when you open an old project in version 27 or later. To enable/disable the UI audit, go to the "Display" tab, "Help for edit" group and check or uncheck "UI audit". If the UI audit is enabled, you will see the following when you open a window or page that uses an old feature: - The
 icon appears in the upper-right corner of the element (Table or Combo Box control, for example). - A tooltip appears when hovering over the icon.
- Clicking the icon opens a popup window. In this window, you can:
- fix the problem. In most cases, you can directly fix the problem by clicking "Fix" in the popup window.
In some cases, if the fix requires changing an option, the popup window allows you to open the control description to make the change. - deactivate the tip: the error display for this field will then be cancelled.
Reminder: Deactivated errors can be reactivated from the context menu of the compiler errors pane, option "List of deactivated errors" (shortcut: Alt + I). - use the context menu at the top of the popup window to:
- Select the control.
- Open the control description window.
- Temporarily disable errors for this control. Errors will be re-enabled the next time the element containing the error is opened.
- Temporarily disable errors for all controls. Errors will be re-enabled the next time the element containing the error is opened.
Tip: the link at the top of the popup opens the control description window.
Remarks: - UI audit errors can also be activated on reports.
- UI audit errors concerning windows or pages are also displayed when running the static audit on the project. You can also fix the detected problems from the static audit window.
Enabling or disabling UI audits for all projects You can enable or disable UI audits for all projects. For WINDEV or WINDEV Mobile: - Display window editor options: under the "Home" pane, in the "Environment" group, pull down "Options" and select "Window editor options"..
- On the "Controls" tab, select or deselect the "Disable UI audit for all projects" option.
- Validate.
For WEBDEV: - Display page editor options: under the "Home" pane, in the "Environment" group, pull down "Options" and select "Page editor options".
- On the "Controls" tab, select or deselect the "Disable UI audit for all projects" option.
- Validate.
For the report editor: - Display the report editor options: under the "Home" pane, in the "Environment" group, pull down "Options" and select "Report editor options".
- In the "Preferences" tab, select or deselect the "Disable UI audit for all projects" option.
- Validate.
Examples of detected problems The UI audit can highlight errors in the controls: - an HTML control still in IE6 mode (which prevents modern content from being displayed correctly),
- a Chart or Shape control for which anti-aliasing has not been enabled,
- a Camera control in an old version,
- any control for which a new useful option is available but has not been enabled,
- a Combo Box control that can be made resizable or set to auto-size,
- a field does not offer help for entering file masks,
- There is no Validation button in the window or page. A button with one of the following labels is not a Validation button: OK, Apply, Validate, Save, Finish, etc.
- There is no Cancel button in the window or page. A button with one of the following labels is not a Cancel button: Cancel, Close, Abort, Quit, Ignore, Return, etc.
 New in version 2025In a report with an array, there is no total displayed for numerical columns. The automation creates a body complement containing the totals. New in version 2025An image is very large, so the display can be slowed down.
More general problems are also detected: - Use of a background image with transparency but without clipping (thus consuming unnecessary resources),
- An Internal Window control that points to an Internal Window not found in the project,
- Binding to an non-existent item or variable,
- Control not compatible with the current configuration,
- Control too small to be touchscreen-friendly,
- Conflicting anchors,
- Multiple fields using the same logical name,
- 2 OK or Cancel buttons in a window,
- ...
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|