Then the users performs an action that changes this something, and then the resizing-bug resurfaces again. Our CTO tried to explain it like this: with an update, something (we also don't know what exactly) gets reset that triggers this bug. It also happened that the resizing-bug vanished for a while after our customers started MAXQDA in "safe mode", but a short while after, the bug reappeared. Unfortunately, with those customers that are affected by this bug, it happens that resizing will work and then seize to work again with updates. I've just forwarded your question to our Chief Technology Officer and he explained the situation to me: ![]() Thank you for letting us know about this issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |