Quoting querido <[email protected]>:
Pardon me, I'm not an expert.
No problem, thanks for your feedback!
There are troubleshooting tools that can step through one statement at a time, right? And there are methods for stepping through larger blocks, like printing to a log or pop-up boxes that say "...start function x...", "...end function x...", "...start function y...", "...end function y...", etc., right? But you can't do this because the bug doesn't occur on your machine.
Indeed. The problem is that I suspect that the issue is not in Mnemosyne's own Python code, but rather in the C code of one of the libraries Mnemosyne uses. So, using a debugger to step through the Python code would probably not be very helpful.
Still, it could be worthwhile doing this to validate this assumption. Running Mnemosyne in a debugger is not possible with the one-click installer, but is possible with the multi-click installer. I could provide some instructions later on on how to do this if anybody is interested.
Cheers, Peter -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
