ricktu wrote: |
probc2 wrote: | I could just imagine what their support department is replying back to you with as well "send screenshots", and "we cant reproduce the problem". I've been down that path a number of times with them on various bugs with virtually no resolution.
|
Actually they did respond when I contacted them about it. They said they knew about the bug and it has been fixed in the latest version but they would not fix it in my version (14) because work on it has been closed off.
While I can appreciate that pretty much all development companies close off development work at some point for past versions they have an awful lot of their customers still working on versions 14 and 15 however this is a major bug that is causing them to lose goodwill with their customers so not fixing it is a bad business decision. Especially when it must be a very minor fix. Comment out the line of code that opens the reminder if they wanted to be quick about it.
|
I can also understand why they made such a decision. If they have fixed it in their latest version then it's good. I'm not saying it is a good decision, although I think it is a risky one, for those who are bothered by the bug they would have to ultimately choose whether to upgrade or switch.