Support Board
Date/Time: Wed, 15 Jan 2025 16:00:19 +0000
Winhook WH_MSGFILTER is not working anymore for the chart window
View Count: 1236
[2017-07-14 18:00:46] |
T29_Dev1 - Posts: 22 |
We use WH_MSGFILTER window hook to implement hot keys in our studies. It was working up to ~1568 version. In 1580 it's not working - I see no one message from the chart window in WH_MSGFILTER, but it catches messages from other SC windows like the message log window. (note: I can see all messages when I use WH_GETMESSAGE hook) What has been changed and can WH_MSGFILTER be working for the chart window in the future? Thanks. |
[2017-07-17 17:15:14] |
Sierra Chart Engineering - Posts: 104368 |
This will be fixed 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
[2017-07-17 17:52:59] |
onnb - Posts: 662 |
Do you have expected build number for us to look out for ?
|
[2017-07-17 21:52:19] |
Sierra Chart Engineering - Posts: 104368 |
Yes, version 1585. We will try to get this out, late this evening.
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 |
[2017-07-19 21:05:39] |
Sierra Chart Engineering - Posts: 104368 |
We thought we knew what the problem is but the particular user who you use this for, is still experiencing the problem even after reverting back the change that we made that we thought was causing this problem. We certainly can figure out what the issue is, but we do not think that time is productive when really you should be using a properly implemented solution. It really is best that we add a new feature to ACSIL to pass through both the character events and keyboard events through to ACSIL functions that have requested them. This will be out in the next release. These will be the new variables: sc.ReceiveKeyboardEvents sc.KeyboardKeyEventCode sc.CharacterEventCode 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 |
[2017-07-19 23:41:34] |
Sierra Chart Engineering - Posts: 104368 |
We have completed the development of the new API. Below is an example function for it. This will be supported in the next release. SCSFExport scsf_ReceiveKeyboardEventsExample(SCStudyInterfaceRef sc)
{ SCString MessageText; // Set configuration variables if (sc.SetDefaults) { sc.GraphName = "Receive Keyboard Events Example"; sc.StudyDescription = ""; sc.GraphRegion = 0; sc.FreeDLL = 0; // We have expressly set Autolooping to off because we are not filling // in any of the Subgraph[].Data[] arrays. Since Autolooping will // cause this function to be called for every bar in the chart it // would be inefficient to use Autolooping. sc.AutoLoop = 0; sc.ReceiveKeyboardKeyEvents = 1; sc.ReceiveCharacterEvents = 1; return; } // wait for an event if (sc.KeyboardKeyEventCode != 0) { MessageText.AppendFormat("Received keyboard key event. Windows virtual key code: %i, ", sc.KeyboardKeyEventCode); sc.AddMessageToLog(MessageText, 0); } if(sc.CharacterEventCode != 0) { MessageText.AppendFormat("Received character event. ASCII code: %i, ", sc.CharacterEventCode); sc.AddMessageToLog(MessageText, 0); } } 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-07-19 23:42:03
|
To post a message in this thread, you need to log in with your Sierra Chart account: