Change of columns in the maintable not possible; arrangement not stored 5.0DEV

[hsvia]

Hi together, I really appreciate your work !

The arrangement of the maintable should be operated as communicated in #4456.

You can rearrange the columns and adjust their width directly in the maintable. That is stored and restored

The problems appear with the 2 win-systems referenced at the end.
Please do not treat me as a duplicate of #4437, my different libraries generate additional problems.

Below the arrangement before closing and after saving:

Now the arrangemet after closing and reopening the program

This is the arrangement after just closing and reopening the libraray

This is the arrangement after opening another library with a total different columns.

The relevant columns are missing.
I do not know how to restore a layout with the demanded columns with 5.0-DEV ?
The shifting and resizing of the columns works, even though the arrangement is not stored.
But I see no way to exchange the columns of the old library with the columns demanded.

After opening the lib with 4.31, closing and opening with 5.0-dev

one can restore the correct arrangement reloading the preferences.

This is working, but definitely not comfortable.

Nevertheless, many thanks for the great program!

JabRef 5.0-dev--snapshot--2018-11-04--master--185c47a7a
Windows 8.1 6.3 amd64
Java 1.8.0_191

AND

JabRef 5.0-dev--snapshot--2018-11-04--master--185c47a7a
Windows 10 10.0 amd64
Java 1.8.0_191

[hsvia]

Hi together,

there are actions leading to a "reset" of the arrangement:

1. every time one resizes the jabRef program window
2. every time one resizes the groups window
3. Most times when one selects different groups from the group window

I hope this helps

JabRef 5.0-dev--snapshot--2018-11-04--master--185c47a7a
Windows 8.1 6.3 amd64
Java 1.8.0_191

[tobiasdiez]

This should be fixed in the latest development version. Could you please check the build from http://builds.jabref.org/master/. Thanks! Please remember to make a backup of your library before trying-out this version.

[bernhard-kleine]

This is not solved as well as #4224.