?List of all solved function restrictions VisiWinNET Smart Version 6.5.4.1 to 6.5.5:
?Devlopment VisiWinNET Professional:
- Projektexplorer: Projects could be displayed several times in the VisiWinNET Projektxplorer.
- Communication: When renaming a channel, the text keys for the variables of this channel have not been adapted.
- Rezepteditor: The label of the recipe manager was not translated.
- Power Tags: The number of PowerTags was incorrectly determined during development time in some situations.
- Variable browser: When variables and structure members were transferred, the existing texts and comments were overwritten, although the browser returned the value zero for these properties.
- Language switching: No texts could be inserted or overwritten into the text groups of the lowest hierarchy via the clipboard.
Control Elements:- AlarmList / AlarmLine: AlarmList / AlarmLine: Alarm class icons were incorrectly drawn if they contain black pixels.
- AlphaPad: The AlphaPad had a wrong keyboard layout in Italian and Spanish.
- ComboBox: ComboBox did not set the SelectedIndex to -1.
If the list was deleted and re-filled and the same SelectedIndex was set, this entry was not visible, the ComboBox remained empty. - Events - FormChangeMode: The "FormChanging" event was not triggered with the direct commands "ProjectForms.Hide", "ProjectForms.Close" and "ProjectForms.Unload".
- Forms: The TabControl did not scale correctly (Tablaschen, ScrollButtons, TabPages) for form scaling using the method "Form.Scale (SizeF factor)".
- ListView: The ListView control also used the data for invisible columns for automatic height calculation of the individual ListViewItems.
This made the item too high if a column with a lot of text was invisible. - PrintHandler: Printing alarm and recipe lists had not worked.
- RecipeList: The ReciepList triggered an UpdateView event during disposing.
- RecipeList: Did not display the recipe files if the RecipeClassHandler was initialized after RecipeList.
- Slider (+ ExtendedSlider): The focus rectangle did not work correctly.
In addition, the EditControl property did not work. When the StopEdit (false) function was called, the slider did not return to the original position. - ScaleDateTime: The ScaleUnit, RulerMajorAlign, and RulerMinorAlign properties had an incorrect default value.
- ScaleDateTime: AutoAlignment.UseWeek had no effect.
- ScrollBar: For very large values ??for property Maximum, there was an overflow (OverflowException)
- TabControl: Anchored controls have been incorrectly positioned in TabControl.
- TrendChart: Triggering the zoom rectangle also responded to the right mouse button. As a result, no context menu could be opened.
- TrendChart: The first call to ResetResolution after creating a form did not work.
- TrendChart: If the trend is first zoomed and then scrolled using the TrendTime control, the TrendChart drew too many subdivisions in the time axis.
- TrendLegend: Property Alignment = Left did not work for columns: after closing and loading the form, the setting was gone.
- TrendTime: Did no longer worked with property DisplayMode = ScrollBar when the TrendChart was zoomed.
- Toolbox Category Draw - Shape森林舞会游戏: The ShapeContainer did not put itself back into the background when another control was pushed into the background. As a result, those controls in the designer were no longer selectable, or no longer clickable at runtime.
- VarIn: If a VarIn was placed on a base form in a container with the modifier = protected, no changes occurred when the form was derived.
Runtime Compact:
- UserManagement: Changing the password of a domain user did not work.
- Communication: Access type one time reading (1xR) for variables did not work. The variables were always read.
- Communication: Variables or structure elements of type Write or ReadOnce have been registered in communication groups with sampling rate 'Always' for cyclic reading.
- Trend system: The delete variable of a trend archive had no function at runtime.
- Variables: The internal data type for bit accesses to integer variables was incorrect.
If the notation Item.Name = "Alias <.Nr>" is accessed by one bit in an integer variable, the data type is now "VT_BOOL". - Alarm system: AlarmManager.SetAlarm ("Name") triggered alarm with wrong time stamp (1.1.0001)empel aus (1.1.0001)
Runtime Standard:
- Communication: Substitute values ??are now entered for all Bad Qualities, not only for NOT_CONNECTED.
- Communication: If text variables (VT_BSTR) with more than 1500 characters were written, the VisiWinNET manager crashed.
- Communication: Fields of structures could not be created with size 1 at least value 2 was neccassary.
- VWSetBit: VWSetBit with 0th bit from Boolean variable did not work.
- OPC UA: Unknown variables in the OPC UA server did not set the quality to Bad.
- OPC UA: Activation mode = Triggers for communication groups did not function correctly with OPC UA.
- Language switching: Free alarm parameters can be entered in different languages ??but could not be shown changed in the selected language at runtime (text was then empty).
- Trend system: In historical trend data queries over several files, a horizontal line sometimes appeared in the trend control.
- Recipesystem: If you load a main recipe via a Load Trigger Variable, only the load event of the main recipe was triggered.
