enhancement
critical
major
minor
minor
#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
defect
Problem:
If a selection (with or without CTRL) is performed in the grid or a table component using TableControl, two selections are always triggered, with all the consequences and implications that entails.
The reason for this is that the selection is first cleared and then reset. The selection must be set only once with the correct values.
Code Migration
Since this bug is quite old and is likely responsible for various workarounds, an application’s selection behavior must be thoroughly reviewed, and any workarounds may need to be reversed. Components dependent on the SelectionChannel should also be taken into account here.
Unfortunately, no general instructions can be provided for this.
Test
The problem occurs specifically in the following situation:
- You have a component A that depends on a grid via the SelectionChannel, does not support null as a model, and is displayed as the second tab in a tab bar next to the grid.
- If Component A is visible and you change the grid’s selection, the tab jumps back to the first tab, even though the tab containing Component A could also be displayed with the new selection.
- After the bug is fixed, the tab containing Component A remains visible when the grid’s selection changes.