It's not unreasonable to expect that, but its even more reasonable to expect it not to happen.twisted-space wrote:So would it be unreasonable to expect an email back saying something like "confirmed, we have no idea what is causing it but we're looking into it"?Angstrom wrote: Probably because they were able to reproduce it, unable to figure out why it was happening and hence to give any estimate on anything realting to it.
And it turns out the reason for THAT was - it was a sylenth bug, which sylenth have now obviously fixed.
At least that seems the self-evident answer to me.
Unexpect the expected, and you are on the right track.
I have a vivid mental image of the bug tracking process, it starts off with polite customer service types like Dennis and Amo, but the hard bugs naturally go deeper and deeper into a programmer cave, where they only speak in guttural grunts. Your bug went into the programmer cave. Nobody was brave enough to go see where it went.
I'm sure Dennis will confirm that this is exactly how it works