[GEM-dev] [pd-gem:bugs] #202 extremely high cpu usage when using GEM in a tiling wm

["IOhannes m zmölnig" via GEM-dev]

- **labels**: rendering (e.g. display) --> rendering (e.g. display), linux
- **Group**: linux --> 0.93.3



---

** [bugs:#202] extremely high cpu usage when using GEM in a tiling wm**

**Status:** open
**Group:** 0.93.3
**Labels:** rendering (e.g. display) linux 
**Created:** Fri Dec 14, 2012 09:43 AM UTC by defaultxr
**Last Updated:** Fri Dec 14, 2012 09:43 AM UTC
**Owner:** nobody

I use a window manager called StumpWM, and the default behavior of the window manager is to maximize all windows within their "frame". when i try to open a gem window via the \[gemwin\] object, the window manager and GEM get stuck in a "resizing fight", with the window manager attempting to resize the GEM window, and GEM attempting to reset the size. it works fine if i use a floating window group \(which does not cause the window manager to try resizing the window\), but i prefer not to have to do that. it also works if i send a "dimen" message to \[gemwin\] with the precise dimensions that StumpWM will try to resize the window to, but if i attempt to split the window-frame, the problem comes back.


---

Sent from sourceforge.net because gem-dev at lists.iem.at is subscribed to https://sourceforge.net/p/pd-gem/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pd-gem/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20140708/50a135a1/attachment-0001.html>