new thinkpads vs. dyalog special keystrokes
Posted: Thu Apr 08, 2010 12:52 pm
I've been using <Shift-Esc> to quit the Dyalog session editor for decades. It recently began to fail when I purchased a new Lenovo Thinkpad, Model X201s (the lightest, fastest, smallest one available that still had a full-size keyboard.) At first I thought it was a Dyalog/Windows7 issue, but have since been able to prove that the problem lies with some unspecified Lenovo preloaded software and/or drivers. So far Lenovo has not been that sympathetic, probably because there aren't that many applications in the world that rely on <Shift-Esc>.
Has anybody else encountered this?
One workaround is to simply redefine Dyalog's keyboard, but that would mean changing all development machines. And I don't yet know whether any other keys are similarly effected. (Re-programming 25 years of neural pathways is not easy either.)
Another is to wade through the unsupported techinque of creating a special build of the operating system without Lenovo "value-added" software. The problem here is that there's probably some software that is genuinely useful.
A third approach is to somehow force Lenovo to fix the problem, since it's their mistake. They already can use their own propriety purple <Fn> key, to make all the private key-combinations they will ever need. They really have no need to start co-opting legal Windows key combinations.
The fourth approach is to return the machine (there are 2 days left in the 21 day return period). Unfortunately, that would mean losing the many days I've invested in configuring the new machine.
Suggestions anyone?
Has anybody else encountered this?
One workaround is to simply redefine Dyalog's keyboard, but that would mean changing all development machines. And I don't yet know whether any other keys are similarly effected. (Re-programming 25 years of neural pathways is not easy either.)
Another is to wade through the unsupported techinque of creating a special build of the operating system without Lenovo "value-added" software. The problem here is that there's probably some software that is genuinely useful.
A third approach is to somehow force Lenovo to fix the problem, since it's their mistake. They already can use their own propriety purple <Fn> key, to make all the private key-combinations they will ever need. They really have no need to start co-opting legal Windows key combinations.
The fourth approach is to return the machine (there are 2 days left in the 21 day return period). Unfortunately, that would mean losing the many days I've invested in configuring the new machine.
Suggestions anyone?