Community
Participate
Working Groups
Build Identifier: There is an issue with the order for injected columns. Lets asume that a table page defines some fixed columns (with java) and some injected columns (which will be added at runtime). Scout shows first of all all java-defined columns and than all injected columns. An improvment of this concept will be if the developer would have the possibility to define an order. The difference is that java-defined columns have an initial order. It is defined by the @Order annotation of the column. But in general is a inital order missing. Therefore I suggest to added an initial order index for columns. So that it will be possible to mix the occurrence of java-defined columns and injected columns. Reproducible: Always
Created attachment 211526 [details] Path addes an initial order for IColumns. IColumn defines methods for getting and setting an inital order index. The AbstractTable considers that initial order index.
Thanks for the patch, Adrian. Applied a modified version: o the property is called viewOrder instead of initialOrderIndex o the view order can be changed at any time and the ColumnSet is re-validated on every update o resetting the column order still checks a column's visibility and whether it is displayable at all
Comment on attachment 211526 [details] Path addes an initial order for IColumns. added missing iplog flag
Bugfixes shipped on Scout 3.7 branch
