Topic category: Feature requests and ideas for MCreator
A long-standing problem on Mcreator (at least on the Mac builds) is that clicking gets canceled way too easily. The problem is that you need your pointer to bee 100% still for the duration of the click for it to register. For example, when I want to add something to a slot in a recipe element, I might need to click multiple times because my mouse pointer moves like a pixel or two, and that cancels the click. It shouldn't cancel the click because of slight movement, or even with any mouse movement. That could be excusable in some places due to the click and drag box to select a lot of elements, but in any case, it should be less sensitive. This issue alone makes adding a lot of recipes or duplicating mod elements just a bit more irritating, since I may need to click twice or even three times as much. Before development halts this should be updated, because it would make things so, so, SO much better, and doesn't seem like that difficult of a fix.
Have you had this problem with any other software? I've never run into this issue in my ~4 years of using MCreator.
I have not had this problem with any other software, at least not nearly as bad as Mcreator. Clicking is perfectly fine on all other applications, on Mcreator I just can’t click without holding my mouse still. If it helps, I run on a Mac with a wireless Logitech mouse. This has been a problem that has persisted over many updates, it’s inescapable for me
Unfortunately, I am woefully unexperienced with Mac computers, so any response I could give you would be be a very basic "front-page-of-google" type of answer. Are you using a snapshot version?
System Preferences > Trackpad > Tracking Speed
I don't use a trackpad. I use a mouse. Besides, even if mouse speed were the issue, I'd still place fault on Mcreator for this. Literally every app I have works great except for mcreator in this way. I don't want to have to change any mouse speed settings for one application.
I do not use a snapshot version, its plain ol 2020.4, and the issue has persisted in every version I've used, way before even the GUI update.
Nope, not a snapshot version. The issue was present before this update, its been there since long before the interface update.