This thread is only addressed at the specific issue with opening event dialogs with very large projects. This issue appears to be worked around in r251, so closing. If you have any other issues, please file new issues following all the guidelines, otherwise we can't investigate them. Please keep separate issues in separate threads; it's confusing to pile multiple issues in to one report.
The fix in r251 is based solely on avoiding calls in to Windows. This proves that the issue is in Windows and not C2 itself. Despite the fact these kinds of issues can be extremely difficult to do anything about, we still managed to work around it anyway. Please note that in this case blaming C2 was jumping the gun! Next time it could be C2's fault, but we don't know for sure until the issue is resolved. So please take note that there is no reason to rant about how terrible C2 is before anyone knows what the problem actually is yet.
I am amending the bug report guidelines with the following. The list below is derived from this thread, which has examples of every one. In future if a similar thread is posted I would stop investigating it, based on these new rules.
[quote:l9ejscvt]
Don't troll the developers
Our staff are here to help you. We have experienced engineers who have dealt with thousands of bug reports. The vast majority of reporters are helpful and are happy to work with us. However if you don't co-operate or are unnecessarily combative in dealing with staff, we will close your report and stop investigating it. We will resume investigation on the report if someone files it complying with the guidelines.
The following list are behaviors we will see as trolling. If too many of these behaviors occur in one report it is liable to be closed.
- Insisting developers investigate the issue over holidays or weekends. Please be patient.
- Repeatedly nagging developers to investigate an issue ahead of schedule, or repeatedly bumping the thread.
- Exaggerating the impact of an issue, or otherwise acting as if your issue is so serious, it is the end of the world. This is rarely the case, especially if the issue is not new. Diverting attention can also end up postponing work on other genuinely more serious issues, harming other users. It is also unnecessarily aggravating.
- Constantly treating the developers with scepticism or distrust. We are not perfect, but we are experienced engineers. Please have a little faith. Sometimes we discuss the issue and make educated guesses. However there is no need to try to argue us down every time we say something; it is simply a waste of everyone's time.
- Throwing in unrelated bugs or gripes. Please don't muddy the waters by talking about unrelated issues, complaining about why your favourite feature is not implemented yet, etc. Fixing a bug is difficult enough as it is, and having a concise, focused approach gives us the best chance of fixing it.
- Blaming us before the issue has been fully identified. All software depends on a wide range of third parties, such as OS developers, compiler and library authors, driver developers, browser makers, and so on. We do routinely fix or work around issues which are not directly our fault, in order to try to make sure Construct works as well as possible. If we point to a third-party cause, it does not necessarily mean there is nothing that can be done about it, although it may make it significantly more difficult. Our normal routine investigation simply involves identifying the root cause before we proceed to mitigating it. There is no reason to launch in to a rant about how it's our fault. Often this is simply incorrect and may also cause embarrassment.
- Demanding a resolution when none is practical. Some issues will have no good resolution, such as an issue caused by a specific graphics driver version on a particular OS and hardware combination. It is not feasible to investigate such issues, particularly if the evidence suggests the problem is not in our code. It is also unreasonable to demand an explanation of the inner workings of these other pieces of software we've had no part in developing.
- Accusing us of not responding or not caring about the issue, particularly after we have already put effort in to responding or investigating it
- Arguing about whether or not what you did qualifies as trolling or not ("meta-trolling"). It is up to the judgement of our staff.