New version (Windows 11 64x v9.14.1.2402053)

hmm, I can't reproduce that one, does it happen always?

I uninstalled and reinstalled the program. For now, the bug has not occurred again. It may have been some error in the previous installation process.

Oops! The error occurred again. But now I’ve identified how it happens: whenever I disable the “File name” metadata and enable the “Series” metadata.

Another bug I just found: when I do a search and the results appear, if I just select a certain comic without opening it, and then switch to another comic view, the search results disappear and the screen returns to the top of the library list.

I noticed more instabilities in version 9.14. When starting the program, all metadata headers (below the cover flow) appear marked, even though they were not marked by me. At another time, some headers do not appear, even if marked.

Have you been going back and forward between versions?

I would appreciate if you take screenshots when you see this happen.

When I did the first installation of version 9.14 and detected the bugs that I reported to you, I returned to the previous version (9.13), as I always keep a backup of the current library. Later, I installed the fixed version (9.14.2.2402061) and, during use, I noticed the instabilities that I mentioned later. So I returned once again to version 9.13 and will wait for possible corrections. Unfortunately, I did not think to take screenshots. In future versions, if I find any bugs, I will make sure to take a screenshot and send it to you. I take this opportunity to thank you for your work and attention. YACReader is simply the best software of its kind.

I decided to reinstall the YACReader-v9.14.2.2402061-winx64-7z-qt6 version to test if the bugs would reoccur. Yesterday, after the installation, everything went normally. I did not change the metadata header settings and left it in default mode. Today, in the morning, when checking the library, all metadata headers were marked. So I unchecked Volume, Series and Story Arc. But the grid, as you can notice, remains insistently this way, with the metadata Size space abnormally extended.

i.imgur.com/o5ku7A3.jpeg

the table tries to take all the space available for the last column