04-18-2013, 04:35 AM
I'm not sure that it was fixed. Honestly, we could put a lot of time into fixing this, or we could devote that time into basically rewriting most of the back end and front end code, to support the new xulrunner and sqlite.
By doing those, the next version should have it fixed...but I don't personally have the resources to find the cause of this issue myself. One of the other devs may be able to, though.
By doing those, the next version should have it fixed...but I don't personally have the resources to find the cause of this issue myself. One of the other devs may be able to, though.