# How about having a GLFW\_KEY\_ESHIFT?

**URL:** <https://discourse.glfw.org/t/how-about-having-a-glfw-key-eshift/151>\
**Category:** support\
**Created:** [May 15, 2004, 6:20pm UTC](https://discourse.glfw.org/t/how-about-having-a-glfw-key-eshift/151 "2004-05-15T18:20:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [May 15, 2004, 6:20pm UTC](https://discourse.glfw.org/t/how-about-having-a-glfw-key-eshift/151/1 "2004-05-15T18:20:09Z")

</div>

**anonymous** wrote on [Saturday, May 15, 2004](https://sourceforge.net/p/glfw/discussion/247562/thread/721f70f7/#bd1b):

I have a suggestion: There should be a value for testing whether either shift key is being pressed; call it ESHIFT (E for either).

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [May 18, 2004, 6:28am UTC](https://discourse.glfw.org/t/how-about-having-a-glfw-key-eshift/151/2 "2004-05-18T06:28:52Z")

</div>

**[marcus256](https://sourceforge.net/u/marcus256/)** wrote on [Tuesday, May 18, 2004](https://sourceforge.net/p/glfw/discussion/247562/thread/721f70f7/#bd1b/5949):

Or plain GLFW\_KEY\_SHIFT :)&nbsp; The implementation would not be perfectly logical (so far one key = one event = one code), but on the other side not exactly impossible either. I’m aware of the irritations that dual checks cause, but changing one thing (SHIFT) would mean that other changes would come naturally (Enter/Return), keypad numbers vs non-keypad numbers, etc, etc, and I’m not ready to take that step yet.