2 - The Visualization Editor in CoDeSys

The arrow keys can be used to change from a selected element to a neighbouring one in any direction.

The <Space bar> is used to execute an activity on the selected visualization element. If the element is one which has a text output variable, a text input field will be opened which displays the text contents of the variable. Pressing the <Enter> key writes in this value.

Additional key (combinations) for the online operation can be defined in the configuration dialog 'Keyboard usage'. There also the keys <Tab>, <Space> and <Enter> can get assigned another functions than the above described standards.

The individual elements of instances behave in Online mode identically to the corresponding ones in the visualization that is instanced. They will therefore react the same way as individual elements to inputs and operation by mouse and keyboard; the display of tooltips in instances is also elementdependent. When processing the element list, as for instance when jumping from one input element to the next using the tabulator, the processing of all individual elements of a instance proceeds from the location of the instance in the element list before jumping to the next element of the list.

Note: Operation over the keyboard in online mode is of greatest significance, if the visualization should be used with CoDeSys HMI resp. as Target-Visualization or Web-Visualization !

'File' 'Print' in online mode

'File' 'Print'is used to print out the contents of the visualization window in online mode. Visualizations which stretch over the border of the window can lead to inconsistencies particularly when there are moving elements in the visualization.

2.9Visualizations in libraries...

Visualizations can also be stored in libraries and thus be made available to projects in the form of library POUs. They can be inserted as instances or they can be called up via the command „Zoom to vis." in the input configuration of another visualization which is part of the project.

Note: Visualizations used in a project must have unique names. It can be problematic if for instance a visualization from a library is called or referenced which has the same name as one present in the project. Because, in processing instances or visualization calls in the program, first the visualizations in the project, and only thereafter the ones in the loaded libraries will be implemented.