View Single Post
Old 11-13-2022, 10:08 PM   #319
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Quote:
It won't let me reload saved configurations
I am not sure what your issue exactly is yet, but be aware that MCS will not save duplicate copies of preexisting saved criteria. It checks for prior existence, and only then saves the current criteria in the Tab.

To clarify, when you click the "Load Previously Saved Criteria?" pushbutton, it does not show a list for you to select and load, correct?

According to your debug log, you have ~22 saved TXT Query named criteria.

You debug log shows that you were using the "Manage Saved Criteria" pushbutton. That is entirely different from the "Load Previously Saved Criteria?" pushbutton. Where is your issue? Managing or Loading?

I need a debug log showing when you clicked the "Load Previously Saved Criteria?" pushbutton, and selected an item in the displayed list. Then, exit MCS (but not Calibre yet, since your debug terminal session might disappear.).

Your debug log was not created from the command line, and there was nothing after you exited "Manage Saved Criteria" which is not what you described as an issue. I need to see a debug log just for clicking the "Load Previously Saved Criteria?" pushbutton.

Run "calibre-debug -g" in a terminal command line, perform the steps described above, and then select all of the terminal debug log text, copy it, and then paste it into a .txt file. Post that .txt file.


ADDED:
I just released a new version of MCS that forces Qt to immediately update the MCS GUI rather than waiting until it got around to doing it (if it ever did), which might be the cause of your issue. I also improved DEBUG logging related to your issue.



DaltonST

Last edited by DaltonST; 11-15-2022 at 11:29 AM. Reason: new comments
DaltonST is offline   Reply With Quote