# Glfw 2.7.8 OS X flagsChanged issue

**URL:** <https://discourse.glfw.org/t/glfw-2-7-8-os-x-flagschanged-issue/553>\
**Category:** support\
**Created:** [April 27, 2013, 6:30pm UTC](https://discourse.glfw.org/t/glfw-2-7-8-os-x-flagschanged-issue/553 "2013-04-27T18:30:32Z")\
**Posts on this page:** 1\
**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:** [April 27, 2013, 6:30pm UTC](https://discourse.glfw.org/t/glfw-2-7-8-os-x-flagschanged-issue/553/1 "2013-04-27T18:30:32Z")

</div>

**[liamstask](https://sourceforge.net/u/liamstask/)** wrote on [Saturday, April 27, 2013](https://sourceforge.net/p/glfw/discussion/247562/thread/f2f34d52/#a672):

Hi!

I’ve observed that after using the shift-cmd-4 key combination used in OS X to take a screenshot, that the shift key release state is not propagated in glfw. That is, my glfwSetKeyCallback doesn’t fire, and calls to glfwGetKey() show the shift key as still pressed.

I’ve added the following workaround locally within cocoa\_window.m: [http://pastie.org/7729967](http://pastie.org/7729967). In my application, I’m only relying on glfwGetKey() for this behavior so this works fine, but I haven’t investigated further to determine the appropriate strategy for dispatching this change as an event.

I’m happy to prepare a patch to address this if that’s helpful, otherwise just a heads up 🙂

Liam