Enhancement
Critical
Major
Detail
Detail
#25907
Layout editor: inconsistent behavior of unfold state, selection and reaction to object creation
#25951
Application tests: CheckLabeledExecutabilityOp fails to assert non-executability of literal ResKey reasons.
#25952
Model Editor: Enum default provider does not work for enum references for which singleton link storage was explicitly selected
#26002
ConfigurationItem-valued properties with format annotations may cause an attempt to create abstract config items when deserializing null values
#26012
Help editor crashes when a user has chosen a language that is not in the supported languages of the application
#26039
Gridcomponent: Display of context menu for new (transient) row object leads to UnsupportedOperationException
#26085
An attribute of type tl.model.search:Expr is not displayed in the form above a TL script editor
#26111
Context menu commands for table rows are erroneously executed on the table model when opening the context menu in the background of the table
#26153
Migration: Replay fails if string values with line breaks are contained in the dataset where a line ends with a semicolon
#26171
A TL script expression entered in a wizard template is reformatted when transferred to the final template
#26223
TL script: Under unfavorable conditions wrong parameter values when evaluating local functions
Bugfix
Problem:
If a selection is executed in the grid or a table component with TableControl (with or without CTRL), two selections are always triggered, with all the consequences and the whole entourage.
The reason for this is that the selection is first deleted and then reset. The selection may only be set once with the correct values.
Code migration
Since this bug is quite old and probably responsible for various workarounds, the selection behavior of an application must be checked in detail and possibly workarounds must be turned back. Components dependent on the SelectionChannel must also be taken into account here.
Unfortunately, a general instruction cannot be given for this.
Test
The problem occurs especially in the following situation:
- One has a component A dependent on a grid via the SelectionChannel, which does not support null as a model and is displayed as a second tab in a tabbar next to the grid.
- If component A is visible and you change the selection of the grid, the tab jumps back to the first tab, although the tab with component A could also be displayed with the new selection.
- After fixing the error, the tab with component A remains visible when changing the selection of the grid.