The stupidest case of manual-not-read-itis I ever seen.
mtPaint is designed as a compact and responsive tool for literate sapient beings. Integrating into it nursery facilities, such as context menus, tooltips, and context help, for the sole benefit of the entitled personages who cannot deign to read a single page from the included manual, would waste my time, and swell the binary to the detriment of the users with weak hardware.
I believe the people who dislike to read, learn, and know, will go for the newest shiniest toy on the market anyway, having no understanding and no use for any sort of advanced features. Not my target audience, and given that I work on mtPaint primarily for my own needs, no loss either.
Having said that, if you indeed have managed to crash mtPaint and it is reproducible, I am very interested in learning the conditions leading to that happening. Because I do not tolerate bugs in my software, but to fix a bug, I need to know how to make it trigger.
Noel Santos
Administrator
That's okay. You're not the target audience for my review either, because you already know how to use the software you made yourself.
Sure I can reproduce it. Here's how to crash mtPaint on Linux Mint:
1) click in Help -> Keyboard shortcuts... I'd love to know why this menu item is in the Help menu instead of in the File or Edit menu, by the way, because I had a lot of trouble finding it.
2) bind "Pan Window" to the space bar.
3) hold the space bar AND hold the left mouse button then move the mouse cursor around. After a while, mtPaint will crash.
wjaguar
Visitor
Agreed. In my epoch, illiteracy was a condition to be ashamed of, not to flaunt around.
Anyhow, your attitude is your own problem and your own punishment, and as it happens, the scheme you describe happens to do NOTHING on my Slackware system. Therefore, the brokenness of your favorite distro is not MY problem in any way, shape, or form. Good luck! (you'll need it)
wjaguar
Visitor
After quite some trying, I managed to reproduce the bug you described. It did indeed exist.
Therefore, you do deserve the honor of being the discoverer of the weirdest bug ever, in all those 20 years of mtPaint. :)))
The specific mixed triple-stack of input events, hitting a GLib2 bug, is definitely not a thing I would ever trigger on my own.
So, thanks. While the fix is irrelevant to normal use, stability under heavy load is good to have.
Discussion of: My Review of mtPaint
The stupidest case of manual-not-read-itis I ever seen.
mtPaint is designed as a compact and responsive tool for literate sapient beings. Integrating into it nursery facilities, such as context menus, tooltips, and context help, for the sole benefit of the entitled personages who cannot deign to read a single page from the included manual, would waste my time, and swell the binary to the detriment of the users with weak hardware.
I believe the people who dislike to read, learn, and know, will go for the newest shiniest toy on the market anyway, having no understanding and no use for any sort of advanced features. Not my target audience, and given that I work on mtPaint primarily for my own needs, no loss either.
Having said that, if you indeed have managed to crash mtPaint and it is reproducible, I am very interested in learning the conditions leading to that happening. Because I do not tolerate bugs in my software, but to fix a bug, I need to know how to make it trigger.
That's okay. You're not the target audience for my review either, because you already know how to use the software you made yourself.
Sure I can reproduce it. Here's how to crash mtPaint on Linux Mint:
1) click in Help -> Keyboard shortcuts... I'd love to know why this menu item is in the Help menu instead of in the File or Edit menu, by the way, because I had a lot of trouble finding it.
2) bind "Pan Window" to the space bar.
3) hold the space bar AND hold the left mouse button then move the mouse cursor around. After a while, mtPaint will crash.
Agreed. In my epoch, illiteracy was a condition to be ashamed of, not to flaunt around.
Anyhow, your attitude is your own problem and your own punishment, and as it happens, the scheme you describe happens to do NOTHING on my Slackware system. Therefore, the brokenness of your favorite distro is not MY problem in any way, shape, or form. Good luck! (you'll need it)
After quite some trying, I managed to reproduce the bug you described. It did indeed exist.
Therefore, you do deserve the honor of being the discoverer of the weirdest bug ever, in all those 20 years of mtPaint. :)))
The specific mixed triple-stack of input events, hitting a GLib2 bug, is definitely not a thing I would ever trigger on my own.
So, thanks. While the fix is irrelevant to normal use, stability under heavy load is good to have.
I'm glad you were able to reproduce it. :)
You're welcome!