From: Guido S. <__g...@we...> - 2005-02-27 15:22:27
|
Did Jonatan's message of doom stop everybody from trying the latest OroboROX? Thing is, except the dysfunctional "Revert" button, I'm not having the problems outlined by Jonatan. Meanwhile I've upgraded from Xorg-6.7.1 straight to Xorg-6.8.2 (never tried 6.8.1) and everything is still working fine. So can't be too much of a "works for me" situation. Jonatan, do you have a "AutoRepeat" option in your Xorg.conf/XFree86.conf? Please remove the line and try again. You can set the option with ROX-Session's Keyboard tool. I'm saying this, because I had trouble in the past with a bogus default AutoRepeat value, which lead to a modifier appear as "stuck". Probably thousands of modifier key events queued up or something due to rapid autorepeat. Anyway, nothing I can do now. Can't fix what isn't broken for me. When I still get no response I'll release this version officially and see what happens. PS: Now that I have the XComposite prerequisites, I'm peaking into the issue a bit, stealing the code from xfwm4 HEAD. |
From: Jonatan L. <th...@ho...> - 2005-02-27 16:32:06
|
On Sun, 27 Feb 2005 16:22:05 +0100 Guido Schimmels <__g...@we...> wrote: > Did Jonatan's message of doom stop everybody from trying the latest > OroboROX? Naahh, it ain't no doom. works great other than those small issues... =) > Thing is, except the dysfunctional "Revert" button, I'm not having the > problems outlined by Jonatan. Meanwhile I've upgraded from Xorg-6.7.1 > straight to Xorg-6.8.2 (never tried 6.8.1) and everything is still > working fine. So can't be too much of a "works for me" situation. Do you have a MS windows keyboard? > Jonatan, do you have a "AutoRepeat" option in your > Xorg.conf/XFree86.conf? Please remove the line and try again. You can > set the option with ROX-Session's Keyboard tool. I'm saying this, > because I had trouble in the past with a bogus default AutoRepeat > value, which lead to a modifier appear as "stuck". Probably thousands > of modifier key events queued up or something due to rapid autorepeat. I don't have any AutoRepeat option in my XF86Config, but I do have the autorepeat checkbox turned on in the keyboard configlet... I tried unchecking it, and the autorepeat was turned off but OroboROX behaved as usual - it didn't fix the problem. Personally, I'm OK with the workaround I found: Pressing both my "Win" keys as Window Ops modifier in keyboard GUI, then it works as it should! But, I also take this as evidence of the problem beeing easy to fix, and I think it should be fixed. =) PS. Did you fix the missing unshadow button on shadowed windows? /Jonatan -=( http://kymatica.com )=- |
From: Guido S. <__g...@we...> - 2005-02-27 19:05:53
|
On Sun, 27 Feb 2005 17:36:21 -0300 Jonatan Liljedahl <th...@ho...> wrote: > On Sun, 27 Feb 2005 16:22:05 +0100 > Guido Schimmels <__g...@we...> wrote: > > > Did Jonatan's message of doom stop everybody from trying the latest > > OroboROX? > > Naahh, it ain't no doom. works great other than those small issues... =) But looks like it freaked out everybody else :) > > Thing is, except the dysfunctional "Revert" button, I'm not having the > > problems outlined by Jonatan. Meanwhile I've upgraded from Xorg-6.7.1 > > straight to Xorg-6.8.2 (never tried 6.8.1) and everything is still > > working fine. So can't be too much of a "works for me" situation. > > Do you have a MS windows keyboard? Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" Option "XkbVariant" "nodeadkeys" Generic el-cheapo PC keyboard. > Personally, I'm OK with the workaround I found: Pressing both my "Win" > keys as Window Ops modifier in keyboard GUI, then it works as it should! > But, I also take this as evidence of the problem beeing easy to fix, and > I think it should be fixed. =) Could you please check what's written to keyboardrc in either case! Is there a problem with the GUI fucking up the config only - or does OroboROX misbehave with a proper config? Maybe a few sanity checks in the GUI shortcut capture code will do. > PS. Did you fix the missing unshadow button on shadowed windows? Yep. |
From: Jonatan L. <th...@ho...> - 2005-02-27 23:17:51
|
On Sun, 27 Feb 2005 20:05:35 +0100 Guido Schimmels <__g...@we...> wrote: > > > Did Jonatan's message of doom stop everybody from trying the > > > latest OroboROX? > > > > Naahh, it ain't no doom. works great other than those small > > issues... =) > > But looks like it freaked out everybody else :) Come on now, people! Try out this beast and flood us with bugreports! ;) > > > Thing is, except the dysfunctional "Revert" button, I'm not having > > > the problems outlined by Jonatan. Meanwhile I've upgraded from > > > Xorg-6.7.1 straight to Xorg-6.8.2 (never tried 6.8.1) and > > > everything is still working fine. So can't be too much of a "works > > > for me" situation. > > > > Do you have a MS windows keyboard? > > Option "XkbRules" "xorg" > Option "XkbModel" "pc105" > Option "XkbLayout" "de" > Option "XkbVariant" "nodeadkeys" > > Generic el-cheapo PC keyboard. Mine says: Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "se" > > Personally, I'm OK with the workaround I found: Pressing both my > > "Win" keys as Window Ops modifier in keyboard GUI, then it works as > > it should! But, I also take this as evidence of the problem beeing > > easy to fix, and I think it should be fixed. =) > > Could you please check what's written to keyboardrc in either case! > Is there a problem with the GUI fucking up the config only - > or does OroboROX misbehave with a proper config? If I press one of them I get "Super", if I press both I get "Super+Super". Nothing wrong with the GUI here, it's OroboROX that is missbehaving. > Maybe a few sanity checks in the GUI shortcut capture code will do. For example, I've managed to get a blank shortcut button several times.. (when it missbehaves, I have to hold down my Super key for OroboROX to interpret my clicks as normal ones, so I hold it when I click the shortcut-button, and when I then release it I get a blank button, and then I can click it again to set it...) /Jonatan -=( http://kymatica.com )=- |
From: Guido S. <__g...@we...> - 2005-02-28 17:33:02
|
On Sun, 27 Feb 2005 17:36:21 -0300 Jonatan Liljedahl <th...@ho...> wrote: > On Sun, 27 Feb 2005 16:22:05 +0100 > Guido Schimmels <__g...@we...> wrote: > > > Did Jonatan's message of doom stop everybody from trying the latest > > OroboROX? > Personally, I'm OK with the workaround I found: Pressing both my "Win" > keys as Window Ops modifier in keyboard GUI, then it works as it should! > But, I also take this as evidence of the problem beeing easy to fix, and > I think it should be fixed. =) But what's written to keyboardrc in either case, this I need to know. |
From: Ken H. <ke...@ha...> - 2005-02-27 23:33:24
Attachments:
ken.vcf
|
Guido Schimmels wrote: >Did Jonatan's message of doom stop everybody from trying the latest OroboROX? > > I really didn't have any need to upgrade since I really never use any WM keyboard shortcuts. I'll check it out anyway to verify that nothing else is broken for me. >PS: >Now that I have the XComposite prerequisites, I'm peaking into the issue a bit, stealing the code from xfwm4 HEAD. > > Just installed xfwm4 to play around a bit. I'd certainly welcome the eye-candy. Running 6.8.2 here also. Noticed that with xcompmgr any window size change messes up the display (window shade, filer auto size). Hope that having this in OroboROX is the solution. |
From: Guido S. <__g...@we...> - 2005-02-28 09:49:58
|
On Sun, 27 Feb 2005 15:43:25 -0800 Ken Hayber <ke...@ha...> wrote: > Guido Schimmels wrote: > > >Did Jonatan's message of doom stop everybody from trying the latest OroboROX? > > > > > I really didn't have any need to upgrade since I really never use any WM > keyboard shortcuts. > I'll check it out anyway to verify that nothing else is broken for me. There are important bugfixes too, like with maximizing only horizontally or vertically working properly now. And fullscreen mode didn't work with some apps (Helix-/RealPlayer) > >PS: > >Now that I have the XComposite prerequisites, I'm peaking into the issue a bit, stealing the code from xfwm4 HEAD. > > > > > Just installed xfwm4 to play around a bit. I'd certainly welcome the > eye-candy. Running 6.8.2 here also. Noticed that with xcompmgr any > window size change messes up the display (window shade, filer auto > size). Hope that having this in OroboROX is the solution. How is it with xfwm4? Is it usable? Usable only width NVIDIA's drivers or work other cards/drivers too? I guess the backing store may work well enough with more cards. Additional eye-candy like shadows, transparency and stuff will depend on proper driver support, I'm afraid. |
From: Ken H. <ke...@ha...> - 2005-02-27 23:56:29
Attachments:
ken.vcf
|
Jonatan Liljedahl wrote: >On Sun, 27 Feb 2005 20:05:35 +0100 >Guido Schimmels <__g...@we...> wrote: > > > >>>>Did Jonatan's message of doom stop everybody from trying the >>>>latest OroboROX? >>>> >>>> >>>Naahh, it ain't no doom. works great other than those small >>>issues... =) >>> >>> >>But looks like it freaked out everybody else :) >> >> > >Come on now, people! Try out this beast and flood us with bugreports! ;) > > > Ok, after several minutes of banging on it I found one issue and one ??? item. 1) If you clear the 'Win operation modifier' shortcut all hell breaks loose! No, really. OK, mouse clicks on the window borders are normal, but virtually all mouse clicks inside the window do not do what you want. For instance, Double clicking on Filer icons does a Window shade. Shift click does the normal filer operation. I tested with all other modifiers set to none and it works as expected. 2) I don't know when this changed, but currently if a window is shaded it cannot be maximized or minimized. Don't know if that is intentional or not. I'm kinda on the fence about whether I like it or not. |
From: Jonatan L. <th...@ho...> - 2005-02-28 16:15:19
|
On Sun, 27 Feb 2005 16:06:32 -0800 Ken Hayber <ke...@ha...> wrote: > >Come on now, people! Try out this beast and flood us with bugreports! > >;) > > > > > > > Ok, after several minutes of banging on it I found one issue and one > ??? item. > > 1) If you clear the 'Win operation modifier' shortcut all hell breaks > > loose! No, really. OK, mouse clicks on the window borders are > normal, but virtually all mouse clicks inside the window do not do > what you want. For instance, Double clicking on Filer icons does a > Window shade. Shift click does the normal filer operation. I tested > with all other modifiers set to none and it works as expected. I think this is what happens when I set my "win ops modifier" to Super ("Windows" key). It behaves as if I did _always_ hold down my win ops modifier. So dragging with the mouse inside a window moves it, etc... > 2) I don't know when this changed, but currently if a window is > shaded it cannot be maximized or minimized. Don't know if that is > intentional or not. I'm kinda on the fence about whether I like it > or not. I think it's the right thing, at least when it comes to maximizing... On the other hand, I can't see why it should be forbidden to minimize a shadowed window! /Jonatan -=( http://kymatica.com )=- |
From: Tony H. <h...@re...> - 2005-02-28 00:05:12
|
In <200...@we...>, Guido Schimmels wrote: > Did Jonatan's message of doom stop everybody from trying the latest OroboROX? It works for me with at least one bug from 0.9.5 fixed - minimising in one direction at a time - and no new ones that I noticed. But I'm not as adventurous with my keyboard settings as Jonatan. I noticed the problem with Firefox thinking it's starting maximised when it isn't, but only on one of my PCs (not the one I'm using now with 0.9.6). I think I may still be running 0.9.5 on the other one, but I only built it recently so it "feels" newer. I have the same problem with kshisen on this PC though, and when I click the maximise button it jumps from one monitor to the other (Xinerama). Some wishes, in approximate order of priority: OroboROX only seems to honour struts for windows being maximised or for snapping during drags. I'd like them to also apply to newly-opened windows. The pointer should update when it's over a draggable border, not only when you're dragging. I sorely miss the caption showing the current geometry when moving or resizing a window that many other window managers show. A "quick 'n' dirty", but perfectly adequate alternative would be to show the geometry in the window's title bar. -- TH * http://www.realh.co.uk |
From: Ken H. <ke...@ha...> - 2005-02-28 14:53:51
Attachments:
ken.vcf
|
Guido Schimmels wrote: >On Sun, 27 Feb 2005 15:43:25 -0800 >Ken Hayber <ke...@ha...> wrote: > > > >>Guido Schimmels wrote: >> >> >> >>>Did Jonatan's message of doom stop everybody from trying the latest OroboROX? >>> >> really didn't have any need to upgrade since I really never use any WM >>keyboard shortcuts. >>I'll check it out anyway to verify that nothing else is broken for me. >> >> > >There are important bugfixes too, like with maximizing only horizontally or vertically working properly now. >And fullscreen mode didn't work with some apps (Helix-/RealPlayer) > > Never had any problems (don't use fullscreen mode or h/v-maximize) > > > >>>PS: >>>Now that I have the XComposite prerequisites, I'm peaking into the issue a bit, stealing the code from xfwm4 HEAD. >>> >>ust installed xfwm4 to play around a bit. I'd certainly welcome the >>eye-candy. Running 6.8.2 here also. Noticed that with xcompmgr any >>window size change messes up the display (window shade, filer auto >>size). Hope that having this in OroboROX is the solution. >> >> > >How is it with xfwm4? Is it usable? Usable only width NVIDIA's drivers or work other cards/drivers too? >I guess the backing store may work well enough with more cards. Additional eye-candy like shadows, transparency and stuff will depend on proper driver support, I'm afraid. > > > I have an old ATI Radeon 7500 pci card wth a P3-1.3Ghz. Both xcompmgr and xfwm4 support shadows with noticeable slowdown, but I could live with it. I'm pretty sure it is just software rendering here. I enabled RENDER acceleration but saw no difference. The only real difference here is that xfwm4 has nicer looking shadows and no artifacts when the screen resizes. Transparency is far too slow to be useable. |
From: Guido S. <__g...@we...> - 2005-02-28 17:46:55
|
On Mon, 28 Feb 2005 07:03:47 -0800 Ken Hayber <ke...@ha...> wrote: > >There are important bugfixes too, like with maximizing only horizontally or vertically working properly now. > >And fullscreen mode didn't work with some apps (Helix-/RealPlayer) > Never had any problems (don't use fullscreen mode or h/v-maximize) RealPlayer fullscreen works a little different than others. With previous releases it was practically unusable with OroboROX. Maybe more important is the fix in handling withdrawn windows, which affected Scribus, which was also basically not usable before. As Scribus is one of a kind in X11 DTP, that was pretty bad. > >How is it with xfwm4? Is it usable? Usable only width NVIDIA's drivers or work other cards/drivers too? > >I guess the backing store may work well enough with more cards. Additional eye-candy like shadows, transparency and stuff will depend on proper driver support, I'm afraid. > > > > > > > I have an old ATI Radeon 7500 pci card wth a P3-1.3Ghz. Both xcompmgr > and xfwm4 support shadows with noticeable slowdown, but I could live > with it. I'm pretty sure it is just software rendering here. Yes. and neither xcompmgr nor xfwm4 make use of SIMD targetted code. So CPU rendering has much room for improvement. But I'll have to wait for others to write the MMX/SSE/Altivec code for that. >I enabled > RENDER acceleration but saw no difference. The only real difference > here is that xfwm4 has nicer looking shadows and no artifacts when the > screen resizes. RENDER is always enabled when available. The config file option has no effect. > > Transparency is far too slow to be useable. That's probably has to be GPU rendered or turned off. The Star Trek Future, I'm afraid (-> long off), |
From: Jonatan L. <th...@ho...> - 2005-02-28 16:22:03
|
On Mon, 28 Feb 2005 00:04:59 +0000 Tony Houghton <h...@re...> wrote: > Some wishes, in approximate order of priority: > > OroboROX only seems to honour struts for windows being maximised or > for snapping during drags. I'd like them to also apply to > newly-opened windows. I'd like this too! I have set it to open windows at mouse cursor, and everytime I open a window by clicking something on my panel, the window is opened covering the n-pixel border... > The pointer should update when it's over a draggable border, not only > when you're dragging. Yes. > I sorely miss the caption showing the current geometry when moving or > resizing a window that many other window managers show. A "quick 'n' > dirty", but perfectly adequate alternative would be to show the > geometry in the window's title bar. My alternative window-cycling-feedback thing could be used for it. I've written code to display a message at the center of the screen, it could easily be used to display the geometry in the center of a window while moving or resizing it... /Jonatan -=( http://kymatica.com )=- |
From: Jonatan L. <th...@ho...> - 2005-02-28 17:20:17
Attachments:
geometry_box-0.9.6-lijon.patch
|
On Mon, 28 Feb 2005 17:26:19 -0300 Jonatan Liljedahl <th...@ho...> wrote: > > I sorely miss the caption showing the current geometry when moving > > or resizing a window that many other window managers show. A > > "quick 'n' dirty", but perfectly adequate alternative would be to > > show the geometry in the window's title bar. > > My alternative window-cycling-feedback thing could be used for it. > I've written code to display a message at > the center of the screen, it could easily be used to display the > geometry in the center of a window while moving or > resizing it... Done! Patch attached. There's an option for it in the Window config GUI. NOTE1: It shows the box in the middle of the current screen, not the middle of the window. I thought this was the best way... NOTE2: While moving a window, the position displayed are the one of the actual window content, not including the titlebar. Should I subtract the titlebar width/height? /Jonatan -=( http://kymatica.com )=- |