grapesmoker
commented
5 months ago Hey, just want to respond to this re: development.
As the original developer of QEMS2 I simply have not had time in the last few years to devote any attention to it at all. Earlier this year I got some breathing room to work on a new version of QEMS and made some progress, but then family and work took over and I just have not been able to give this project the time it requires. The basic problem with QEMS2 is that the code base is very aged and relies on outdated libraries and various code hacks that are holding it together. As a consequence making changes to the code is very hard and requires a lot of work to familiarize oneself with its structure; this is true even for me, since I haven't looked at it in ages. So, I apologize for the fact that I have not been able to fix various bugs in QEMS2 but it's a huge pain in the ass to do. I am hoping to take up QEMS3 development again in the coming months and of course the goal will be to avoid many of the problems that plague this iteration.
That said, I will try to look at this problem and, at the very least, either prevent this action from happening or create a set of reasonable defaults. I can't promise that it will happen quickly but I will do my best to fix it in the near future.
mbentley00
Right now if you move a question to a set where its writer or category does not exist, it does any number of unpredictable things and generates what is effectively a randomly chosen new tag, without throwing up any kind of error or confirmation message alerting the user to this. Every new set shows a new unforseen consequence of this behavior. It makes extremely crucial functions of the program break, such as using the category tags to track set completion and packetize or figuring out how many questions to pay people for.
Unless it is the case that QEMS2 development has been totally abandoned, I strongly urge that fixing this behavior be the #1 priority of anyone who is still working on it.