Support Board
Date/Time: Tue, 26 Nov 2024 00:40:36 +0000
ACS_RECEIVE_POINTER_EVENTS_ALWAYS freezes the graph as long as the mouse moves.
View Count: 965
| [2023-11-10 22:36:40] |
| User462211 - Posts: 18 |
|
Hello, I have a problem, as soon as I add to initialization sc.ReceivePointerEvents = ACS_RECEIVE_POINTER_EVENTS_ALWAYS; this creates strange behavior, since the graph freezes completely as long as the mouse is moving. That is to say that the user must stop moving the mouse, if he wants to be able to see his graph correctly updated. This is behavior that is very problematic. This behavior is for example present in the study scsf_TradingTriggeredLimitOrderEntry. As I have difficulty seeing in which case this blocking behavior of the graph could be desirable, I would tend to categorize it as a bug. Is there a way to fix this problem ? Or at worst bypass it ? |
| [2023-11-11 00:39:25] |
| Sierra_Chart Engineering - Posts: 17178 |
|
This does not surprise us, that there is this problem. But we have never observed this, or ever had reports of a problem like this. Nevertheless we will implement a regulation of the number of time studies are called during mouse move events to eliminate this type of issue. Or at least greatly minimize it. 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 |
| [2023-11-13 12:29:44] |
| User462211 - Posts: 18 |
|
Hello, thank you for your response. Here is the code for my study LP_test: #include "sierrachart.h"
So your suggestion is not possible.SCDLLName("LP_test") /*==========================================================================*/ SCSFExport scsf_LP_test(SCStudyInterfaceRef sc) { if (sc.SetDefaults) { sc.GraphName = "LP_test"; sc.GraphRegion = 0; sc.ReceivePointerEvents = ACS_RECEIVE_POINTER_EVENTS_ALWAYS; return; } } Because I cannot implement a regulation of the number of times study are called during mouse move events, because the current study LP_test already does nothing. Here is a short video comparing the difference in behavior with or without the Study LP_test.dll : https://www.youtube.com/watch?v=fjyIZAPNNM0 To make video capture easier, I did it in replay, but the behavior is exactly the same in real time. |
| [2023-11-13 18:16:10] |
| Sierra_Chart Engineering - Posts: 17178 |
|
The regulation/limiting of events is something that we will do on our side. This is done and will be out in the next release.
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: 2023-11-13 18:16:22
|
| [2023-11-13 20:44:35] |
| User462211 - Posts: 18 |
|
Cool, it's really great. Thank you so much. |
| [2023-12-21 17:19:04] |
| User907968 - Posts: 823 |
|
I guess this change was completed fairly recently? Whatever was done has resulted in a less satisfactory user experience when using custom tools based on pointer events - the interaction seems 'clunky' rather than smooth. The only workaround I can see is to set the chart update interval to very low ms, but I'm not sure that's necessarily desirable either. Maybe there is some middle ground between what is was before and what it is now? |
| [2023-12-22 16:57:43] |
| Sierra_Chart Engineering - Posts: 17178 |
|
Yes we know about that. But this is just how it is. There is a serious problem without regulating the pointer events. We will see if we can make some adjustment to help.
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: 2023-12-22 16:58:14
|
| [2023-12-22 17:13:28] |
| User907968 - Posts: 823 |
|
Ok, I understand. Anything you can do will be appreciated, thanks. |
| [2023-12-26 22:02:43] |
| Sierra_Chart Engineering - Posts: 17178 |
|
What we decided to do is let the user control the interval between these events. You can make this as low as 10 milliseconds. This will be found in the next release under Chart >> Chart Settings >> Performance.
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: 2023-12-26 22:03:17
|
| [2023-12-27 15:57:18] |
| User462211 - Posts: 18 |
|
Thank you, I am getting back to life thanks to this latest update, version 2568 actually solved a good part of the problem. But there are still cases where the problem persists, that is to say that the price remains blocked and nothing is updated on the graph, such as for example: 1) when modifying an order, which remains very annoying. 2) when changing the vertical position of the graph, which is painful, but which is not the most annoying in my eyes. Here is a short video : https://youtu.be/NYznSnT61pk |
| [2023-12-28 19:08:51] |
| User907968 - Posts: 823 |
|
What we decided to do is let the user control the interval between these events. You can make this as low as 10 milliseconds. This will be found in the next release under Chart >> Chart Settings >> Performance.
Thank you, this is excellent.Two questions: 1. Minimum Chart Update Interval In Milliseconds For ACSIL UpdateAlways - which takes precedence out of this and the existing Chart Update Interval setting? 2. Is there any possibility you would consider adding access to these new parameters via ACSIL? |
| [2023-12-28 19:13:23] |
| User907968 - Posts: 823 |
|
But there are still cases where the problem persists, that is to say that the price remains blocked and nothing is updated on the graph, such as for example: 1) when modifying an order, which remains very annoying. 2) when changing the vertical position of the graph, which is painful, but which is not the most annoying in my eyes. So your problem is not isolated to when 'sc.ReceivePointerEvents = ACS_RECEIVE_POINTER_EVENTS_ALWAYS', but occurs at other times also. Is your CPU maxing out? Date Time Of Last Edit: 2023-12-28 19:15:46
|
| [2023-12-29 01:06:48] |
| Sierra_Chart Engineering - Posts: 17178 |
|
1. Minimum Chart Update Interval In Milliseconds For ACSIL UpdateAlways - which takes precedence out of this and the existing Chart Update Interval setting?
The Chart Update Interval still drives the update interval for the chart. If the Chart Update Interval is lower than "Minimum Chart Update Interval In Milliseconds For ACSIL UpdateAlways", then this new setting is the minimum update interval when the studies are only being called for the purpose of sc.UpdateAlways. The studies can be calculated more often according to the Chart Update Interval depending upon if there is another event that can trigger a chart update, for example new market data received. 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 |
| [2023-12-29 01:08:31] |
| Sierra_Chart Engineering - Posts: 17178 |
|
Regarding post #10, you are going to have to figure this out and resolve it. You are the only one who ever has reported a problem with this. We tried to solve this for you, only to the detriment, of other Sierra Chart users and some testing we have done has shown that really the number of study function calls when moving the pointer around, is not really that excessive. We suspect the issue is that you have a poor performing custom study that you have developed. We cannot provide any further help. This is now up to you to figure out and resolve. 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: 2023-12-29 01:10:24
|
| [2023-12-29 12:53:00] |
| User462211 - Posts: 18 |
|
I should have been more explicit. As seen in the video from second 34, I delete all study. So indeed, the problems concerned (the price which freezes) in post #10 have nothing to do with 'sc.ReceivePointerEvents = ACS_RECEIVE_POINTER_EVENTS_ALWAYS' So as there is no Study in the chart, I cannot optimize anything. The problem has nothing to do with the Study. On the other hand, adding Study amplifies the problem, or at least makes it obvious and much more visible. In the video, I reproduce the problem systematically to make it clear what the problem is, but in reality when I trade, my mouse movements are not as fluid, so the problem appears half the time (or once in three). Which gives the impression of a little randomness. Consequently, I attributed this problem to a lack of fluidity in the Denali flow. So in my opinion, I must not be the only one to have thought that. And this problem appears on both my PCs. I asked a colleague to also do the test on his side, and he has the same problem. He told me that he will check the Nasdaq US open when the volatility is higher. Date Time Of Last Edit: 2023-12-29 23:11:27
|
| [2023-12-30 09:10:58] |
| Sierra_Chart Engineering - Posts: 17178 |
|
Regarding performance issues this is the relevant help topic: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often We can only refer you to this. We do not specifically know what the issue is in your case. All known performance issues are documented there. 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 |
| [2023-12-30 23:45:31] |
| User719512 - Posts: 264 |
|
This change, as I have observed in v2576 is great, and the defaults provided seem quite adequate. I also never saw the behavior the OP posted in the video.
|
| [2024-01-03 20:50:52] |
| User462211 - Posts: 18 |
|
However, it is extremely easy to reproduce the problem. My colleague just sent me a short video which I share https://www.youtube.com/watch?v=invBvcUlVwI, where he reproduces the problem very easily. He even noticed something that I hadn't seen, which is that it freezes all of Sierra's chart simultaneously, and not just the chart where the manipulation is done. Here is the chartbook used: |
 Secours.cht - Attached On 2024-01-03 20:47:52 UTC - Size: 3.37 KB - 335 views Attachment Deleted. |
| [2024-01-03 21:02:14] |
| Sierra_Chart Engineering - Posts: 17178 |
|
This is not easily reproduced. This is not a Sierra Chart issue. There is something system specific causing the problem. We are not able to reproduce this.
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 |
| [2024-01-03 22:02:04] |
| Sierra_Chart Engineering - Posts: 17178 |
|
The other thing to check on this is to disable OpenGL and test again if you are using OpenGL: Graphics Settings: Use OpenGL for Chart Graphics (Global Settings >> Graphics Settings >> Other) For performance related issues once again refer to: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often 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 |
| [2024-01-05 17:59:19] |
| Sierra_Chart Engineering - Posts: 17178 |
|
We are not able to reproduce the issue. But we have been looking more at Improving performance, when the pointer is moved around a chart. There are some improvements that will be out in the next release. This will be out today or over the weekend. We will want to know if it makes a difference. If it does make a difference for the better, this would strongly indicate an inefficiency at the operating system level which is something that not all systems would be encountering. Since we do not. 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 |
| [2024-01-06 22:20:14] |
| User462211 - Posts: 18 |
|
I just updated my operating system and drivers. I downloaded and tested version 2580 of sierrachart (and version 2582), on a clean installation of Sierrachart, and I see no difference. My PC and that of my colleague are on Windows 10. (And my second PC is on Windows 7). I even tried this virtual machine (VirtualBox + Windows 10), same problem. And then, without much conviction, I installed a second virtual machine (VirtualBox + Windows 11), the problem disappeared. The price is no longer blocked, with version 11 of Windows. The problem is therefore on earlier versions, from Windows 10. So I'm thinking to see if I can migrate to Windows 11 without too much damage for my other applications. |
| [2024-01-06 22:27:24] |
| Sierra_Chart Engineering - Posts: 17178 |
|
We have never observed this problem and we use Windows 7 and Windows Server 2012 and do not observe the problem. Certainly Windows is a terrible operating system. But certainly Windows 7 is just fine. What we can say with certainty, is that if you are noticing this issue, there is definitely something wrong at the operating system level because there is really very little processing that goes on when moving the pointer around even when using the Chart Values tool. The Tool Values window gets updated but that is a highly efficient, table/list that is developed by us, probably 100 times faster than the trash from Microsoft. We would also expect the vast majority of other users not to experience this. Being we have never noticed this and we know that the processing is quite efficient and especially with the optimizations done on 2582, hard to believe anyone would notice a problem. We can certainly look for more areas of performance improvements, but there is very little processing going on. However, on high resolution systems, there are a lot of mouse move events being generated. So perhaps that is the problem thinking about this some more. So it is not so much the fact that there is a small amount of processing but if that small amount of processing is being magnified by a thousand times maybe it does cause an issue. So before spending more time consider the resolution of the display device. If the resolution of the display device is a problem then we would have to regulate in some way, the number of mouse/pointer move events getting processed. But we would make this user adjustable the regulation. 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: 2024-01-06 23:00:20
|
| [2024-01-06 23:40:55] |
| User462211 - Posts: 18 |
|
Your words made me think. With this notion of saturation of events. So, I tried several pointer devices on my native Windows 10. And indeed I have different results. With : * the Logitech G502 SE HERO mouse (well-known wired mouse) or * with the Veikk A50 graphics tablet, i have the problem. On the other hand, with * the Microsoft Sculpt Ergonomic Desktop mouse (wireless mouse combined with a wireless keyboard and wireless digital pad pack) or * the Wacom Bamboo CTH-460 graphics tablet, i have no problem. We are going forward. The problem is therefore not necessarily linked to the operating system. On the other hand, as I observed an improvement using Windows 11 (but under a virtual machine), it is possible that Windows 11 better manages the large quantities of information generated by some peripherals. Maybe Windows 11 applies a filter, even before events arrive at the application. It is also possible that the virtual machine influences the transmissions of pointer events. But this last hypothesis is less likely, since the problem persisted under Windows 10 virtualize. Date Time Of Last Edit: 2024-01-07 00:39:31
|
| [2024-01-06 23:59:04] |
| User462211 - Posts: 18 |
|
I have just re-tested on my Windows 11 virtualizer, and with my two devices where we noticed the problem (the Logitech G502 mouse or with the Veikk A50 graphics tablet). Of course, the price does not freeze, it moves, but we feel that it is not super fluid with the Logitech G502, but frankly acceptable. Date Time Of Last Edit: 2024-01-07 00:04:48
|
To post a message in this thread, you need to log in with your Sierra Chart account: