Quote from sevensa:
Since you are not replying in your own forum anymore and only here, I believe this is the right place to do this. This was your choice to have chosen to only reply here. I don't see you complaining about not the right place when someone is saying something good about you. If I want to give you kudos, this is the right forum, but if I want to point out something negative, then this isn't?
"Carefully analyzing" reported issues and then reporting back weeks later that this is a confirmed bug which will be fixed in one of the future releases does not qualify as resolving them. Analyzing is the easy part, but resolving the issues is what really matters. I am also not really clear how analyzing support issues is relevant to your broken promises.
I'll make you a deal. Post a list of all the "misunderstandings" and I'll post a list of all the unresolved issues and we can compare notes.
Pointing out that you have committed in your own forum to deliver a feature three releases and almost 18 months ago and then didn't, is not very convincing and founded? Not sure how your logic works here. What would be founded? If you are three years late? Four years?
Of course you have the right. But think about what you are saying. You provide backtesting software, but don't think periodical analysis is important? And of course then there are the issue of your incorrect drawdown calculations which your Support people don't see anything wrong with. Calculating drawdowns correctly must be another feature you have decided against.
Fanus,
I have reviewed your complaints and have to admit that you are right in many respects. Iâll try to answer all of your questions.
1. I believe that you are wrong thinking that we only receive positive comments on ET. We are open to criticism as well. We donât respond to your posts on our forum and donât want to do it here because you give us advice that goes beyond the reasonable dialogue between a customer and a developer. You can criticize us as much as you wish, but it doesnât mean that weâll necessarily respond to your comments. As I already mentioned earlier we wonât respond to your posts on this forum as well.
2. I assume you have never developed software. This is why you donât know that in most cases identifying a problem takes much longer than fixing it. Of course, thereâre cases when a fix involves major changes and is rather a new feature than a bug. However, such occasions are rare. This is why we ask to give us all the available information which speeds up the solution better than any discussions. What you might think is an obvious bug is often not so obvious to our testers â simply because the program is very complex and there are hundreds of scenarios for its use and operation.
3. I am not going to list all of the misunderstandings because it would simply be absurd. I can only say that we spent a lot of time analyzing and responding to the bug reports you sent us to only see public complaints and accusations from you. Also when you contacted our representatives personally to ask for support your tone was definitely different. As for the list of bugs, you can certainly publish it. I believe it would be mutually beneficial both for our customers and for us.
4. Regarding the price scales. We didnât meet the deadlines, but it doesnât mean that weâre not planning to implement this feature in future. At the same time, we have implemented many other features that have taken MultiCharts 3.0 to the new level. For example, you are using Portfolio Backtester asking to fix its bugs and add new features. You must understand that we canât work on everything at the same time.
5. Period analysis is an important but not the key feature. This is exactly why we didnât implement it in the first version. Most probably, weâll implement it in future versions.
6. Drawdown calculation is calculated incorrectly and weâll fix it. According to our specifications we calculate the drawdown based on the open trades. As a result, you can have an equity peak and drawdown at the same time. This happens because there are other open positions that are losing money.
7. Our support staff closely work with the engineers and business analysts. The problem you are referring to resulted from the wrong definition in the business logic. It that particular case, our developers and support representatives were relying on that data.
I hope I have answered all of your questions. We will always be happy to receive bug reports from you but I wonât respond to theoretical comments and advice.
Best regards,
Adrew Kirillov
President
