Re: OTP/EWMH (was Re: AlwaysOnTop xclock)
| Newsgroups | gmane.comp.window-managers.ctwm |
|---|---|
| Message-ID | <20170424095226.6ffbe14d@ulgy_thing> |
On Thu, 13 Apr 2017 17:12:32 -0500 "Matthew D. Fuller" <[email protected]> wrote: > > Definitely could use more testing, [...] > > > > Eyeball reviews sought as well. > > Second call. It's been a couple weeks now, and it hasn't acted or > blown up that I've noticed. Though apart from videos and the > occasional web browser kicking the fullscreen lever, my day to day > doesn't much use OTPage. > > Absent some issue being found, I'll probably land it in a week or so, > so we can move on to release time. Sorry to keep you waiting. From your original description of the EWMH handling code I thought it looked something like this: int EWMH_change_layer(...) { //HUGE FUNCTION } In which case I would have done something like a brute force check. However, the function, and the changes you made are more spread out. I think I can still help, I've run into a similar problem on another project I wanted to unit test (uzbl), but my new idea will take longer. Sincerely, David