Version: 4.5 (using KDE 4.5.0) OS: Linux When opening another file (after one file was open) the categories in the new file are gone. I have to close kmymoney and reopen it to have the categories again. Reproducible: Sometimes Steps to Reproduce: see above. The problem is that this does not happen always, only sometimes! Expected Results: Categories are there as defined before.
I have never seen this. Is there anything in particular about these files?
I am not sure. The roblem really is that this only happens occasionally. Would it help to sen you an anonymous file?
when it happens, can you take a screenshot of the categories? Also, if you can save them as anonymous file, compress them and upload them, it would be great. (Don't forget to compress the files, 'cause there are size limits)
I've seen this before it's an old issue dating back to the KDE3 version. I just haven't been able to find out what is causing it.
Yes, this has already happened in the 1.0.x versions. I just wanted to wait for the 4.5 version to see if the problem persists. I will do a screenshot and send the files to you as soon as it happens again. By the way: This software is great work! I love it. Thank you very much and keep going!
I've just remembered something and I'll post it here as a hint. While developing the accounts model I've observed that if you the accounts list is requested from the MyMoneyFile object before it's completely loaded then the categories get the balances displayed as 0. Running a consistency check fixes it but we should take a look at it by locally adding a code that reads the account list while the file is not completely loaded and debugging to see what causes this behavior. Since this bug usually happens when switching between kmymoney files I assume that some widget requests the account list while the file is not completely loaded thus triggering this behavior.
There is a signal fileLoaded. Perhaps if we add a fileClosed signal, and we prevent the models from updating between those two signals, ie. when the file is closed or it has not been completely loaded, we can prevent the problem.
Cristian: could it be that we already fixed this?
I'm closing this bug since I'm sure it's fixed by this commit: http://websvn.kde.org/?revision=1224575&view=revision This can't happen anymore since: 1. AccountsModel is loaded after the file is loaded 2. AccountsModel is cleared after the file is closed 3. AccountsModel::load() is only called in the above cases so there is no way to reach the situation in which AccountsModel::load() is called while the file is empty which was causing this bug