When an update, that adds at least one new column to the table, is installed and an old session, which is still compatible with the new version of the software, is loaded, the new columns are hidden by default.
When restoring a state columns which are not part of the saved order are assumed as hidden and therefore not displayed.
It is not possible to separate between hidden columns and new columns from the current state.
Although this is a minor problem for the table itself, since new columns can be made visible with the column filter, this is not possible for the embedded table in the dendogram view.
Added a workaround to solve this problem without touching the view state ([2e79d1]).
This avoids a break of session compatibility (although it would be ok for the next update) and adding further information to the view state which is not used in most cases. The workaround is only needed if new columns are added to the table by an update.
Related
Commit: [2e79d1]
Last edit: Philipp Mewes 2018-05-08
floatingTable.getColumnModel().getColumn(floatingTable.getColumnCount() - 1);: does this work if you increase the maxColumn? Or will you just pick the same column multiple times?(1) Changed this.
(2) This was actually a bug. Invisible columns were not hidden. Fixed this ([eac507])
(3) That's right. Unfortunately I'm currently not able to rebase. Message is "Rebase did nothing. HEAD was already up-to-date". Im trying to find a solution for this.
Related
Commit: [eac507]
Last edit: Philipp Mewes 2018-05-08
After successfully rebasing the branch on master, i was not able to push the branch to its origin counterpart. Even not with the --force- or +-option. The changes can be found on the new branch bug-301-master([eac507]). I will also update the referenced commits in this discussion.
Related
Commit: [eac507]
merged in [ec6136]
Related
Commit: [ec6136]