Support Board
Date/Time: Thu, 08 Jan 2026 01:50:12 +0000
Post From: 2852 - Behaviour changes re Keyboard Shortucts and Windows Sounds
| [2026-01-06 13:07:17] |
| User247273 - Posts: 44 |
|
These keys are hardcoded, maybe they should not be hardcoded but they have been hardcoded for more than 15+ years to perform the actions that you are currently seeing in newer versions. So you really cannot use them for keyboard shortcuts in the way that you are.
1. I understand they are hard coded, and have been for many years. I'm just saying that, if I were a software company, I'd be a bit troubled that users who've been able to assign those same keys as shortcuts have had no issues for years and suddenly, now there is an issue. Also, of all the things you might choose to hard code to a shortcut, Prev File and Next File are just about the two least useful choices for professional trading.2. Is there a list of other hard coded shortcut keys anywhere that you could provide so I can rework my shortcut keys to avoid those as well? 3. IF you have hard coded shortucts, it's a straightforward thing to implement a function that won't allow a user to assign those keys to anything else in the Keyboard Shortcuts settings along with some kind of error notifying the user that they're trying to assign a shortcut to a hard coded key. Also... In my early years of using this software (starting in 2018), I pretty much never experienced meaningful issues with the platform, but in recent years, it seems more common for pretty noticeable/disruptive bugs to be present in your software releases. It makes me wonder if you guys are getting in over your heads. I've actively recommended Sierra to other traders for years. I've defended your commitment to quality as a counterbalance to the rude arrogance you often display toward your customers. However, I'm not sure I'll be able to keep doing that for much longer. At this point, the removal of MFC for the main window and the child windows, has caused changes with message handling that are not understood at this point in time. But in general the solution is just simply do not use the Alt key in any keyboard shortcuts. We will see if there is a solution to that but just do not use that right now. And we know some keyboard defaults use the Alt key.
You guys are quick to slam the devs over at Microsoft and call them all kinds of names, but now you're starting to sound just like them. "Hey guys, we broke this simple, basic function in the software. We didn't think to tell anyone about it though. Oh, also, We don't know how to fix it yet and we're not sure when we will. Until then, it's on you to sort things out." I have dozens of keyboard shortcuts involving the Alt key that I now need to rework. I guess I'll get started on that as I watch you guys continue slowly turning your software into - well... I'll borrow one of your favorite terms - a "demonic piece of woke trash." Mayube when you're done screwing other things up, you could invite the Windows 11 team over for a pizza party to celebrate the fact that you've finally made it down to their level. |