# Signal for dragging app

**URL:** <https://discourse.glfw.org/t/signal-for-dragging-app/144>\
**Category:** support\
**Created:** [June 13, 2004, 7:36pm UTC](https://discourse.glfw.org/t/signal-for-dragging-app/144 "2004-06-13T19:36:04Z")\
**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:** [June 13, 2004, 7:36pm UTC](https://discourse.glfw.org/t/signal-for-dragging-app/144/1 "2004-06-13T19:36:04Z")

</div>

**[cozman](https://sourceforge.net/u/cozman/)** wrote on [Sunday, June 13, 2004](https://sourceforge.net/p/glfw/discussion/247562/thread/bc88dfc9/#67ae):

I have my application’s internal timer pause when the app loses focus, but if the title bar is held down or the app is dragged, no focus loss is recorded, which is probably correct behavior since the application doesn’t lose focus.&nbsp; Would it be possible to get a glfwGetWindowParam(GLFW\_PAUSED) or similar, or is there another way for me to detect when the title bar has been grabbed.

The problem is that execution is stalled, so if my timer continues to run, when focus returns all objects using time based movement will jump forward all at once, causing major headaches.&nbsp; The pausing on drag can be seen in the following demo (assume normal initialization).

int i=0;  
while(1)  
{  
&nbsp;&nbsp;&nbsp; glfwPollEvents();  
&nbsp;&nbsp;&nbsp; std::cout \<\< ++i \<\< std::endl;  
}

(btw if it matters this is being done on Windows w/ glfw 2.4.2)

---

<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:** [July 7, 2004, 7:26pm UTC](https://discourse.glfw.org/t/signal-for-dragging-app/144/2 "2004-07-07T19:26:09Z")

</div>

**[marcus256](https://sourceforge.net/u/marcus256/)** wrote on [Wednesday, July 07, 2004](https://sourceforge.net/p/glfw/discussion/247562/thread/bc88dfc9/#67ae/daae):

There is currently no mean for detecting this. It may be a problem with how Windows handles moving and sizing of windows (blocking).

It IS possible to detect window resize events during resizes for instance (check your Internet browser), but it has not been implemented in GLFW yet due to some difficulties. It would be VERY nice if I could make GLFW continue to process events and do GL rendering while moving or sizing windows - but as I said, it has not been done yet. It would not change the GLFW API, only the GLFW core.