Impact study

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

Help

Editors

Code editor

Impact study

Overview

How to?

See also

Automatic completion

Automatic procedures

Browser code (WLanguage): Framework 2

Checkers available in the code editor

Code editor: Assisted input

Code editor: Display options

Code editor: Various operations

Code history

Code snippets

Code statistics

Code style

Collapsed code

Conditional target-code

Cross-references in the code editor

Display the code of an element

Environment of code editor

Glossary

Impact study

Importing classes and sets of procedures (text file)

Including the code

Indenting the code

Instant spotting of modified code/current code

Minimap

Multilingual messages: Convert to new format (version 27 and later)

Navigation history in the code

Positioning marks in the code

Recycling the code windows

Reverse code modeling

Server code/Browser code

Showing or hiding empty events or processes of an element

Splitting Business logic / UI code

Translating programming messages

Translating the code

WLanguage

WLanguage code coloring

Overview
How to?
Starting the impact study
Finding out the uses of an element in the project
Applying a change of name to all the elements found in your project

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

Impact study

Overview

The impact study allows you to immediately find out the consequences of the modifications currently performed. An information window is automatically displayed to present the possible ambiguities, the modifications to avoid...

The modifications taken into account are as follows:

renaming or deleting an element handled in the project,
renaming two different elements with the same name,
adding or deleting a parameter to/from a procedure,
...

How to?

Starting the impact study

The impact study is automatically started as soon as a modification that may trigger a problem is performed.

For example:

creating a control with the same name as another project element:
deleting a procedure called in the project:

Finding out the uses of an element in the project

To find out the uses of an element in the project:

On the "Project" tab, in the "Audit and performance" group, expand "Static audit" and select "Cross-references".
Enter the name of the element for which you want to find out the uses in the project.
Click "Find". The list of uses for the selected element is displayed:
Double-click one of the uses of the element to view it.

Remark: This window can remain opened while your modifications are performed in the project.

Applying a change of name to all the elements found in your project

To apply a change of name to all the elements found in your project:

Rename the requested element.
When validating the new name:
- the corresponding errors are displayed in the "Compilation errors" pane.
- a message is displayed in the upper-right corner of the current environment.

This message proposes to automatically rename all the necessary elements.

The rename operation is automatically performed when this message is clicked.

Remarks:

To view all the references that will be modified, select "Impact study of renaming" in the context menu of the error:
You can also start the renaming operation when the new name is validated, by displaying the context menu of the error: