The tree in the editor for the RGM module is not properly initialized under specific circumstances
Summary
Under specific cirumstances the tree for the RGM module in the editor is not properly initialized. The tree is expanded but recipes are not visible. Instead an entry "..." is shown. When interacting with the tree in this state, the editor may close unexpectedly. It can come to this situation when either the recipe tree node is expanded or the variables tree node is expanded, and the group is collapsed, and the uses switches to another module and back again to the RGM module.
Description
Under specific cirumstances the tree for the RGM module in the editor is not properly initialized. The tree is expanded but recipes are not visible. Instead an entry "..." is shown. When interacting with the tree in this state, the editor may close unexpectedly. It can come to this situation when either the recipe tree node is expanded or the variables tree node is expanded, and the group is collapsed, and the uses switches to another module and back again to the RGM module.
Solution
An issue has been addressed in the editor where expanding the tree for the RGM module was not properly handled when re-activating the module in the editor. Now it is assured that the group is expanded first when the variables or recipes are expanded. As a workaround, reloading the project will also resolve the invalid state of the tree for the RGM module.
Information
available from 7.00 SP0 build 1
Issue Number: 26716
Fixed on Date: 3.5.2012
Versions: 7.00 0 BUILD 1
Related Articles
FAQ: It seems that sometimes not all variables are correctly written to the PLC by the RGM module, although the system driver variable states that the recipe was written successfully and the option "write synchronously" is active. How can this be?
When reading a RGM recipe immediately after writing a RGM recipe, with a driver that has the option "keep update list in memory" active, and recipe variables that have been read previously, it can happen that a read cycle is currently in progress, ...
Under specific circumstances the Editor, Runtime, Webserver or zenon Analyzer do not obtain a license from the Codemeter network dongle.
Summary When a system with a Runtime, Editor, Webserver or zenon Analyzer is stopped in an abrupt manner (hard shutdown) the license for this system on a remote Codemeter network dongle is not released. After a restart the runtime / ediotr / ...
The configured keyboard screen is not displayed in the RGM screen when editing a recipe value under specific circumstances
Summary If a keyboard screen is configured for a variable and the RGM screen is opened for editing with a format file of the report generator and the report generator does not contain the action type, the keyboard screen is not opened when editing ...
The webclient closes unexpectedly under specific circumstances in the RGM screen
Summary Performing specific actions in the RGM screen on the webclient, like double click, or two clicks on the action for the recipe variable, or in the value column, can cause the webclient to close unexpectedly. Description Performing specific ...
Editor may stop responding under specific circumstances when the color picker is closed
Summary When picking the color for a property using the color picker in the properties window under specific circumstances the editor may stop responding when the color picker is closed by clicking on another empty area in the screen Description When ...