Support Board
Date/Time: Fri, 12 Dec 2025 09:42:56 +0000
[Sticky] [Locked] - Upcoming Development and Internal Number Precision Improvement Project
View Count: 84
| [2025-12-12 03:13:14] |
| Sierra_Chart Engineering - Posts: 21806 |
|
Several things are going to be posted in this thread, and we will make these as separate posts.
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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-12-12 03:13:36] |
| Sierra_Chart Engineering - Posts: 21806 |
|
First, we want to restate what is posted, in the thread related to the MDI (Multiple Document Interface) development: We are doing some work, related to Minimized windows, and we realize that this whole concept of minimizing a window within the larger MDI container window does not make sense.
When minimizing a window, it goes all the way down to the bottom and usually ends up getting hidden by other windows and you effectively lose it. In some cases it may not even be visible because in the case of the virtual space when enabled, the minimized window is placed all the way at the bottom of the virtual space and you have to scroll down to see it. If other windows are overlapping the minimized window, you have to then move those out of the way. Also you have no idea what window is what among all of the minimize windows at the bottom. They are just a bunch of block rectangles. You can only logically restore it through the CW menu by knowing which one it is and that is not entirely clear. The whole minimize concept within the context of a multiple document interface, does not make sense. Instead what we are going to do is as follows: For minimize, we will support the following: No Action (In which case, there is no minimize button) Hide Window (you can then unhide it, from the CW menu and the hidden windows will be clearly identified) Resize the window to a predefined width and height, that you will set, and keep the top left coordinate in place. So the size of it will be greatly reduced or reduced whatever size you preset. Keeping it in place makes sense. Rather than pushing it all away down to the bottom and having no way to even know what window is what at the bottom. They just look like a bunch of rectangular blocks. It is simply stupid. When a window is is in a reduced resized state, the minimize button, will then act to restore it. In the case of the the main desktop on the operating system, when you minimize a window it minimizes to the taskbar and the taskbar provides a very clear understandable view, of what window is what and you can easily restore them. Minimizing an MDI window, is just simply makes no sense at all and we are going to remove this concept especially being there are various outstanding implementation issues with it. Furthermore, the time and sales window which overlaps the main window and also the market depth window, need to be integrated, into chart windows. We will be adding support to integrate a time and sales into a chart. Market depth is already Integrated in various ways. And we will add support for detachable Chartbooks, but that will take some time. And we are going to complete the project, to support full trade window capabilities through a Control Bar. This will be a highly efficient, and customizable, trading window interface. This will not take long to do. We should have this done, by the end of the day Friday, December 12, 2025. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-12-12 03:21:16
|
| [2025-12-12 03:15:31] |
| Sierra_Chart Engineering - Posts: 21806 |
|
Next areas of development, are as follows: Google firebase integration (a replacement for the ntfy app to receive mobile device notifications for alerts or other chat messages) Two factor authentication for Sierra Chart login (Already in latest Prerelease 2829) Detachable Chartbooks (this will take some time) Control Bar based Trade Window Possibly we may support attaching a quote board into the multiple document interface. Integrated Time and Sales into chart window. Removing, off price trades outside of regular trading hours for CTA and UTP data feeds (stock data). Removing these, will only happen during the nonregular trading hours. No changes during regular trading hours but there is not a problem there anyway. We will have to analyze exactly the particular sale conditions for these off-price trades. Internal precision improvement described in the next post. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-12-12 03:22:16
|
| [2025-12-12 03:20:32] |
| Sierra_Chart Engineering - Posts: 21806 |
|
Another major long-overdue task, that we must do, is that Sierra Chart must support fractional volume/trade/size values. For example US stock market data, from NASDAQ will begin to trade in fractional quantities in February 2026. This is already supported for Market depth data, and it is supported for Trading quantities but it is not supported, for market data volumes for trades. This is also necessary for crypto currency exchanges. We have to go from an integer to a double precision floating point value. This is extensive work which will take 1-2 months. The Intraday data file format will also be adapted to support this. Another critical thing related to the above, is that the internal storage of data within charts needs to go from 4 byte floats to 8 byte double precision floats. This will also improve accuracy with studies. All of the above, will cause incompatibility with ACSIL studies and they will need to be recompiled. This will just be a recompile but inevitably there will be warnings that the compiler will generate. Like for example if you are assigning a value from a Subgraph Data array into a four byte float, then there will be a warning about loss of precision. This can be ignored. Generated DLLs will probably have this new suffix appended after these changes _64D rather than _64. D means double. These changes will increase the memory use of Sierra Chart. The increase would be estimated to be about 80 to 90% more. We would recommend, that a system is equipped with a minimum of 32 GB . This is far more than anything Sierra Chart would ever need, but we just recommend having this amount of memory in a computer system at a minimum. We are thinking in terms of a desktop system. Or a server. We do not believe there will be any performance degradation with the above changes. And once these changes are deployed, it will break compatibility with existing DLLs and they will need to be recompiled and we are not going to be supporting in the current versions, two different interfaces for ACSIL or different versions. Newer versions will simply support the single interface which is updated to use double values. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-12-12 03:56:16
|
| [2025-12-12 03:24:22] |
| Sierra_Chart Engineering - Posts: 21806 |
|
All of the above in this thread, will move Sierra Chart into a much much better class of program which will make it untouchable by any other competition when it comes to features, and capabilities and precision and being everything is developed from scratch. And that we are certain of. It is already good but it is going to be much better. We will then be able to adopt other crypto currency exchanges. We will add support for many more without difficulty. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-12-12 03:25:21
|
To post a message in this thread, you need to log in with your Sierra Chart account:
