Support Board
Date/Time: Sun, 24 Nov 2024 16:43:16 +0000
Most Pointer Events Not Detected
View Count: 368
| [2024-05-07 14:32:37] |
| User462086 - Posts: 196 |
|
Just upgraded to version 2634 from a pre-2577 version. In ACSIL, the 'down' pointer events are no longer detected on each click, only at a fixed interval of 10 seconds regardless of the setting for "ACSIL Pointer Events Minimum Calling Interval." Please help!
|
| [2024-05-07 22:02:19] |
| Sierra_Chart Engineering - Posts: 17156 |
|
There have been no changes with this functionality.
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-05-08 03:35:41] |
| User462086 - Posts: 196 |
|
Thank you for the response. I see there were changes to the Message Log in version 2577. So, the pointer events were being detected by SC, but instead of being printed to the log individually, they were aggregated and printed every 10 seconds.
Date Time Of Last Edit: 2024-05-08 04:31:43
|
| [2024-05-08 07:29:47] |
| Sierra_Chart Engineering - Posts: 17156 |
|
Ok that is true. The logging is the issue. Not the actual events getting through. We did testing now regarding pointer events, and do not see an issue. They are getting through according to the interval. In the next release you will be able to set ACSIL Pointer Events Minimum Calling Interval to -1 to prevent any restriction. 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-05-08 07:30:02
|
| [2024-05-08 07:45:46] |
| User462086 - Posts: 196 |
|
That's wonderful news, thank you!!
|
| [2024-05-08 19:28:29] |
| Sierra_Chart Engineering - Posts: 17156 |
|
This is now released.
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-05-10 15:10:08] |
| User462086 - Posts: 196 |
|
Hi, the change to the minimum calling interval in v2636 didn't help migrating code from v2568 so I've been doing some testing that has yielded interesting results. For reference, the code used for the test study is below. It was compiled in each version tested. When testing for detection of the pointer down events in 2636, initially the events were not detected. Setting the minimum calling interval to -1 remedied this (so I thought) and these events were detected again. Hooray! After removing the test study, saving the test chart with the minimum calling interval set to -1, restarting SC, then adding the study to the same chart again, the pointer down events were no longer detected. Opening the Chart Settings dialog, but changing nothing this time, and then pressing 'okay' magically fixed the issue: the pointer down events were detected once again. Using the zip downloads, I found this behavior started in version 2575 (by testing 2634, 2577, 2576, 2575). In each of these tested versions, I had to open the Chart Settings dialog & press 'okay' before the pointer down events were detected. Versions 2568, 2572, and 2574 detected the pointer down events as expected. No other versions were tested. Thanks for your time. #include "sierrachart.h" SCDLLName("Test_ReceivePointerEvents") SCSFExport scsf_Test_ReceivePointerEvents(SCStudyInterfaceRef sc){ if (sc.SetDefaults){ sc.GraphName = "Test_ReceivePointerEvents"; sc.GraphRegion = 0; sc.AutoLoop = 0; sc.SupportKeyboardModifierStates = 1; return; } int& pv_Counter = sc.GetPersistentInt(0); // disables aggregating of log messages if (sc.IsKeyPressed_Control){ SCString DebugMessage; DebugMessage.Format( "sc.IsKeyPressed_Control: %d", pv_Counter++); sc.AddMessageToLog(DebugMessage, 0); sc.ReceivePointerEvents = ACS_RECEIVE_POINTER_EVENTS_ALWAYS; } if (sc.PointerEventType == SC_POINTER_BUTTON_DOWN){ SCString DebugMessage; DebugMessage.Format( "SC_POINTER_BUTTON_DOWN: %d", pv_Counter++); sc.AddMessageToLog(DebugMessage, 0); sc.ReceivePointerEvents = ACS_RECEIVE_NO_POINTER_EVENTS; } } |
| [2024-05-10 15:27:01] |
| Sierra_Chart Engineering - Posts: 17156 |
|
First of all, there is never any filtering of pointer Down events. That has never been implemented. We would never do that.
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-05-10 15:27:18
|
| [2024-05-10 16:42:46] |
| Sierra_Chart Engineering - Posts: 17156 |
|
We actually understand why there is a problem now in your particular case. You are changing the state of this outside of sc.SetDefaults: sc.ReceivePointerEvents = ACS_RECEIVE_POINTER_EVENTS_ALWAYS; We have to think about how to handle 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-05-11 16:00:54] |
| Sierra_Chart Engineering - Posts: 17156 |
|
We implemented a solution in version 2638.
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-05-12 05:06:27] |
| User462086 - Posts: 196 |
|
My 'pointer' based studies from v2568 are working on v2638. I can't thank you enough!!
Date Time Of Last Edit: 2024-05-12 09:39:24
|
To post a message in this thread, you need to log in with your Sierra Chart account: