Calibre 2.0 Extra Columns in Windows 8.1

[theducks]

Another question:
When you switch libraries, do they have the same structure (custom cols)?

I have 2 libraries with the same structure (Intake on my full Library) and have not seen this (W7x64)

[JSWolf]

Originally Posted by theducks

Another question:
When you switch libraries, do they have the same structure (custom cols)?

I have 2 libraries with the same structure (Intake on my full Library) and have not seen this (W7x64)

Good question. When I last switched libraries and did see the empty columns, I did switch between libraries with different structures.

[BetterRed]

Given most people don't have this problem then its probably something in the existing calibre data rather than the calibre V2.0 install; something that V2.0/Qt5 is 'misinterpreting'

Has anyone with this problem tried accessing their libraries with a vanilla configuration folder - eg via fresh windows portable install.

If the problem doesn't manifest then its presumably something awry in the config data, if the problem is manifest then its presumably something awry in the database(s) - probably in the preferences table(s).

If the former then I would try renaming gui.json and gui.py to gui.*.save and see what happens, if that 'fixes' it then I would... er - offer to send the gui.*.save files to Kovid.

If the latter I would... er - offer to send the database to Kovid.

BR

[JSWolf]

Originally Posted by BetterRed

Given most people don't have this problem then its probably something in the existing calibre data rather than the calibre V2.0 install; something that V2.0/Qt5 is 'misinterpreting'

Has anyone with this problem tried accessing their libraries with a vanilla configuration folder - eg via fresh windows portable install.

If the problem doesn't manifest then its presumably something awry in the config data, if the problem is manifest then its presumably something awry in the database(s) - probably in the preferences table(s).

If the former then I would try renaming gui.json and gui.py to gui.*.save and see what happens, if that 'fixes' it then I would... er - offer to send the gui.*.save files to Kovid.

If the latter I would... er - offer to send the database to Kovid.

BR

I did send my metadata.db file. The thing is, because it only happens on a database switch when it does happen, I would think there's nothing wrong with the actual databases.

[JSWolf]

Kovid, in case this might help debug the problem, I'm attaching my gui.json file from my Windows 7 system. It's running the 32-bit Calibre 2.0.

[BetterRed]

Originally Posted by JSWolf

I did send my metadata.db file. The thing is, because it only happens on a database switch when it does happen, I would think there's nothing wrong with the actual databases.

I think the column width/position data is in the database preferences table, you can see it in metadata_db_prefs_backup.json - look for column_sizes and column_positions.

Just by way of context to my previous post - I have 7 libraries, each of which has a unique set of custom columns - that's why I have multiple libraries

I tried flicking through them with my 64-bit install, I also tried with a vanilla 32bit install with a vanilla config data - no luck at all in seeing the problem.

BR

[kovidgoyal]

I did say that I had made some changes that might help workaround the bug in Qt 5 causing this issue. Wait for todays release.

[JSWolf]

Originally Posted by kovidgoyal

I did say that I had made some changes that might help workaround the bug in Qt 5 causing this issue. Wait for todays release.

I am installing them now. I'll report back what happens. Thanks.