From: Matthew W. O'P. <mat...@ga...> - 2004-10-22 13:46:22
|
-- Jonatan Liljedahl <th...@ho...> wrote (on Thursday, 21 October 2004, 10:52 PM -0200): > On Thu, 21 Oct 2004 16:40:17 +0000 > Guido Schimmels <__g...@we...> wrote: > > OroboROX 0.9.5 > > > > Link: > > http://roxos.sunsite.dk/dev-contrib/guido/ > > > > Changes: > > > > * fixes to get_wm_protocols(): fence post error and fallback to > > XGetWindowProperty() when XGetWMProtocols() fails (from xfwm4) > > * fix bug in handleButtonPress() which would lead to crashes on > > rapid clicks: win = get_mouse_window(dpy, c->frame) -> win = ev- > > > subwindow > > (again from xfwm4) > > * g_mainloop integration > > * more work on ping code (still disabled) > > * some work towards NET_WM_MOVERESIZE > > * fix two silly but harmless bugs in set_allowed_actions_hint() > > * insert "if (!client_exists(c))" safe-guards at various places > > * always focus new transient windows > > > > I didn't revert the modifier init code (xfwm4 -> Oroborus). > > If it still doesn't work everywhere I'd rather get it fixed, because > > > > the new code looks much better overall. > > I might do an interim release (0.9.5.1) with the old code though. > > Still same thing here, the eventhandling is broken. (modifier init > code). Does the new keyboard.c really look that much better? The old one > works (Especially with my ignore_mask stuff, didn't that fix your > numlock problem, Stephen?) > Is anyone else but me having this problem with the new keyboard.c? > > I replaced keyboard.c and did the same change as on 0.9.4 here (or else > I can't use it at all) to see if there are any other bugs: > > * FireFox (0.9) still gets only a close-button. xprop says > _NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, > _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, > _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE. > I don't understand why MAXIMIZE is missing, but anyhow there is > apparently some other problem as SHADE and MINIMIZE is there but not on > the titlebar. It's nice that there is an option to disable this feature > now, though! =) Okay, interesting.... I got to work and read your other emails that you've written in response to mine, and -- guess what: Firefox here at work is showing the exact behaviour you're describing -- no RESIZE or MAXIMIZE hints are set. I suspect that what happened for me last night and yesterday is that I simply killed my previous running version of OroboROX and started the new, so all previously applied hints were retained. Today, now that I've started with a fresh login, I'm seeing these anomalies. Did you get this fixed? I noticed a few code snippets you've posted, but I'm not sure if any of them address this issue. -- Matthew Weier O'Phinney | mailto:ma...@ga... Webmaster and IT Specialist | http://www.garden.org National Gardening Association | http://www.kidsgardening.com 802-863-5251 x156 | http://nationalgardenmonth.org |