I have been an NT user for many years now. I have a professional trading business and I trade every day with NT 64 bit v.7. Of all problems I have encountered in using any platform, the end date not updating is one of the worst. All versions of NT v.7 since it first was released have had this problem. I have reported the problem several times, and I have had technical support look into it, but it has never been resolved. Yesterday it happened again, and I lost several thousand dollars as a result.
The problem description is quite simple: you have all your charts Data Series "End Date" set to the current day. The next morning the charts do not roll to the next day. There is no pop-up that tells you that your charts are not getting a data feed. All windows in fact show you have a valid data feed. Orders, and DOM etc. all show valid active data feeds. But the "End Date" is now yesterday and not today. I have TF 12-13, ES 12-13, ZC 12-13, ZN 12-13. They all were current on 9/16, but on 9/17 they decided, after months of auto-updating to the current day, not to. Well I shouldn't go quite that far, at least 1 month ago. This happens every 1 or 2 months and the last time was about 1 month ago. I also lost money then. Note that I also reboot my computer and restart NT at least once per week.
If I hadn't reported it so many times it would be one thing. But there is always some "reason" given for why it happens. And perhaps Ninja working together with my particular data feed of Rithmic only has a problem. But if tech support only looks for certain cases to solve, then that should be disclosed and I'll trade on another platform.
I was told by tech support in a PM to gather enough people together with this problem to get interest in it being fixed! So if anyone else is seeing this please speak up. What NT support doesn't realize is that people just move to another platform when they see bugs like this. They don't stick around like I have. So you don't realize how serious the problem is.
What I also really don't understand is why they allow the engineers to continue with this architecture? Why don't you have a check box that says, "always stay with the current date if checked"? Then all they have to do is check the end date against the current date and put up a popup, "Warning: end date is out of sync!"
I am a software engineer, and I offered to help architect a solution in the past. It is an easy problem to permanently fix. It is not a matter of fixing this one case or that other one case, which they have done for two years now. It is a matter of fixing all possible cases by putting in a test at the end point, not the starting point.
Now I realize I'm frustrated and I'm trying to be fair, but there really has been a very tepid technical response. I mean, I have a really good track record of finding bugs, and bugs that have been fixed in NT. I don't give anyone a hard time when the bugs get fixed. And I am the kind of customer you want to work with as we can both improve what we do. Thanks for your consideration of this problem.
For other users out there, please speak up if you have ever seen this! I don't personally think this should even be necessary, as such a critical bug should already be top priority, but that is what I was told.
The problem description is quite simple: you have all your charts Data Series "End Date" set to the current day. The next morning the charts do not roll to the next day. There is no pop-up that tells you that your charts are not getting a data feed. All windows in fact show you have a valid data feed. Orders, and DOM etc. all show valid active data feeds. But the "End Date" is now yesterday and not today. I have TF 12-13, ES 12-13, ZC 12-13, ZN 12-13. They all were current on 9/16, but on 9/17 they decided, after months of auto-updating to the current day, not to. Well I shouldn't go quite that far, at least 1 month ago. This happens every 1 or 2 months and the last time was about 1 month ago. I also lost money then. Note that I also reboot my computer and restart NT at least once per week.
If I hadn't reported it so many times it would be one thing. But there is always some "reason" given for why it happens. And perhaps Ninja working together with my particular data feed of Rithmic only has a problem. But if tech support only looks for certain cases to solve, then that should be disclosed and I'll trade on another platform.
I was told by tech support in a PM to gather enough people together with this problem to get interest in it being fixed! So if anyone else is seeing this please speak up. What NT support doesn't realize is that people just move to another platform when they see bugs like this. They don't stick around like I have. So you don't realize how serious the problem is.
What I also really don't understand is why they allow the engineers to continue with this architecture? Why don't you have a check box that says, "always stay with the current date if checked"? Then all they have to do is check the end date against the current date and put up a popup, "Warning: end date is out of sync!"
I am a software engineer, and I offered to help architect a solution in the past. It is an easy problem to permanently fix. It is not a matter of fixing this one case or that other one case, which they have done for two years now. It is a matter of fixing all possible cases by putting in a test at the end point, not the starting point.
Now I realize I'm frustrated and I'm trying to be fair, but there really has been a very tepid technical response. I mean, I have a really good track record of finding bugs, and bugs that have been fixed in NT. I don't give anyone a hard time when the bugs get fixed. And I am the kind of customer you want to work with as we can both improve what we do. Thanks for your consideration of this problem.
For other users out there, please speak up if you have ever seen this! I don't personally think this should even be necessary, as such a critical bug should already be top priority, but that is what I was told.
Comment