Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Mon, 16 Sep 2024 11:29:25 +0000
Post From: Using the TAB key and section 508 compliance
| [2017-09-30 22:05:53] |
| |
|
Let us explain, the basis of post #2. You have made a posting on this board alleging that Sierra Chart is not compliant with US legislation and think this problem is a problem on our side and wanted us to "Fix" the problem. Aside with the noncompliance issue, do you know how many times we hear people blame problems which are not ours and are due to external services or system issues? In the case of external service issues, this is due to stupid programming, incompetency, and total irresponsibility from external services that go on perpetually or for years. We looked at your problem report. We did testing on several systems and could not duplicate it. We thought through what could possibly be the issue and what possible changes have been made that could lead to the issue. There are no changes which should lead to the problem, and if there were, if anything they would be more likely to resolve an issue like this than to cause it. Keyboard shortcuts were a significant consideration as to what the problem could be, and we wanted you to reset those or clear those. We do not even know if you even tried that at this point. You never said. Once we came to a proper conclusion this is going to be a system issue on your side, we clearly expressed that. We want to bring this matter to a close to prevent follow-up postings which take more of our time. This is the basis of why what we said what was said. Now if it is taken in a negative way, we cannot help that but we will take a little time to express some background information. Also, when you use Sierra Chart and you are connecting it with external systems, you are not using a complete solution provided by Sierra Chart. For example when using Interactive Brokers all of the functionality and all the problems you encounter related to that Interactive Brokers system, are not our problem but they often make us look bad and look like idiots. The same goes with TransAct. Whatever issues you experience on the TransAct side and whatever issues you experience with the "bridge" program that we did not develop, which causes issues when using Sierra Chart, also are not our problems but they do make us look bad. And we are not happy about that. We deal with so many external service issues. We get tired of these things and we do not like the bad impression they create. And once again post #9 is not from us. And we are more than happy if you take this thread in its entirety, and provide it to your family member and share it on other forums on the Internet. This is encouraged. And you can also see how much time we waste with stupid exchange policies: About Real-time Futures Data Finally, if you want us to have a look at this, on your side, we can, but it would not be me who would do the remote assistance session. I would have one of our developers do this that I trust with this particular issue. We really just want to validate the problem, and see if anything obvious comes to mind. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2017-09-30 22:09:38
|