Date/Time: Thu, 01 Jun 2023 01:13:44 +0000
Post From: Version 2151 Available: Foundation For Millisecond/Microsecond Timestamping
Sierra Chart Engineering - Posts: 104368
1. In general we do not change functions in order to not break compatibility in a way which requires code changes if we can avoid it.
There is a very good reason why that function returns a double and that is when SCDateTime is passed as a copy either as a return value or as a parameter the GCC compiler handles it differently for unknown reasons than Visual C++ and therefore there is a stack corruption which occurs because there is a slightly different convention/size being used with that parameter type. This is avoided by using a double.
Regarding the other items, the documentation will be updated.
3. You are not the one providing support here. You need to understand, the massive load and the massive complaints we deal with the user support. This is why we do not put Get here. We do not want to put up with the complaints. Understand that! There always is a reason for everything. We can make all kinds of changes to improve things tremendously, but we do not want to deal with all of the dumb questions that get posted here. It really is quite dumb when people basically tell us that their code does not compile, and they can easily look at the documentation and see that function has been renamed and is also documented on the What is New page.
Why do you think we complain so massively about Interactive Brokers. A true garbage service. Complete utter garbage. Our intelligence level is not worth stooping down to that level of garbage for any price. For any price. And when we ask people to pay extra for support which is well justified they do not even want to pay.
Just look at a lot of the nonsense that gets posted on this Support Board . We should start deleting more posts (Which we will do). It is astounding the level of alleged problems that people post which are just simply just nonexistent or are the result of operating system problems or external service issues, or failure to read documentation.
Just look inside of this thread at the things that get posted.
And we decided not to remove sc.FreeDLL even though it is completely unused because we want to have a most studies recompile without any error and eliminate unnecessary support questions.
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:
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: 2020-08-25 09:35:51