> "Is dragging" not trigger on mouse clicks.
Let's say, in my project i already have an event "is dragging" that should trigger on mouse click, me and everybody use it like this since r78, if this will be changed i need to rewrite my project. Now let's say it's not about me, about 10-100 or more c2 users. So a breaking change, that will affect almost everyone who use dragdrop, like this, can be applied only if this change will fix a major bug, "dragging behaviour in C2 should work as it does in every other single computer application" is not really a major bug.
Yes of course if a program rely on the dragging behaviour to work with mouse click it will cause problems if fixed and its annoying.
Its not about it being a major bug or not but whether the behaviour works as intended and it might very well do that as Ashley haven't commented on it, so you might be right that it works as they thought it should and then ill disagree with that, but can accept it.
But a lot of bug fixes and new features in C2 might cause problems in projects as C2 is being developed on the fly. Meaning when I bought it, it couldnt do half the stuff it can now. Looking at the page where you download C2 there are links to a stable version and a beta version. How many programs do you know of that you buy, that constantly release Beta versions? they release updates or patches to fix an already fully functional program with all the feature already available. This is not to say that the way Scirra does it is bad, just that when you release a program this way, making fixes and adding new features all the time things can go wrong that annoys users and causes them to having to change certain things.
For instant I have not long ago made a lot of bug reports regarding the video object causing all sorts of problems, where I had to make lots of workarounds to make my program work. Then I made a report about some audio problem and video, that was fix in r207 and suddenly most, if not all, the other video problems that I made bug reports for have been fixed as well, even though its not stated in the r207 release, so now my program contain a lot of workaround code that needs to be removed. Yeah its a bit annoying now, but its much better that these things now work as you would expect them to whatever the changes Scirra made in r207 that solved them. Then I should complain about that to Scirra as well, because I have to remove my workarounds in my project? that would make little sense, I think its great that they are now fixed.