[Solved] Openbox Ignoring Titlebars, Odd Resizing Problems

Alright, so I'm trying to set up my Openbox to have some manual window tiling support similar to Subtle's implementation.
My screen is 1600x900.  I have 1 pixel margins all around except for a 41 pixel margin on the East side of the screen.
Here are some of the appropriate parts to my rc.xml:
<keybind key="W-KP_3">
<action name="MoveResizeTo">
<x>-0</x>
<y>-0</y>
<width>458</width>
<height>449</height>
</action>
</keybind>
<keybind key="W-KP_9">
<action name="MoveResizeTo">
<x>-0</x>
<y>+0</y>
<width>458</width>
<height>449</height>
</action>
</keybind>
So, if my screen is 900 pixels tall, with 1 pixel margins on top and bottom, that should mean that I have 898 pixels to work with vertically.  898/2=449, so by setting the window the be resized to a height of 449 pixels should mean that the window will take up exactly half of my screen vertically.  Unfortunately, it seems that Openbox does not include the titlebar in all of this so when I have two terminal windows.  This means that when I have a window set to W-KP_3 and another at W-KP_9 (bottom right and top right), the windows will overlap. 
Is there any way to fix this without undecorating my windows?
EDIT: Here's a screenshot of it so you can see the problem.  http://i.imgur.com/NYhyj.jpg
Last edited by iimblack (2011-04-10 20:56:56)

It's just a wee bit of math and a couple of test runs to correct this.  Your title bars plus windows borders appear to be 14 to 20 pixels in height.  So change your desired height from 449 to 433 (16 pixels difference), test it, and adjust the value up or down from there.
If you are using xterm, the window will not necessarily be the full height you specify.  On my display, where I normally don't use window decorations, xterm won't allow a window to include a fraction of a line height.  You might want to run your height tests with a different app.
Here's an old shot of my tiling.  I deliberately leave a gap between tiles.
Last edited by thisoldman (2011-04-10 19:53:42)

Similar Messages

  • [SOLVED] Openbox window titlebar height reduced on maximized windows

    Hello, after a update I have this "problem"
    http://i44.tinypic.com/1498cc6.png
    http://i43.tinypic.com/wlxjcl.jpg
    When the window is maximized the height of the titlebar is reduced
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
    Last edited by Totoxa (2013-08-14 14:59:50)

    I know that latest openbox update modified theme behaviour
    I think it's a theme problem

  • [SOLVED] GNOME 3.8 annoying window resize problem

    Hello all fellow early-adopters :-)
    A very annoying quirk I've noticed, moving from GNOME 3.6 to 3.8, is that it no longer remembers, nor retains, the size/positions I set for many of my application windows. For example, my mail client (Evolution) is sized to fill most of my screen (centrally), with Empathy and Skype as long narrow windows on both sides - giving me a nice, broad "communications" overview on that particular desktop (with dev tools etc open on others).
    On 3.6, this layout was retained during my session, as well as next time I started these apps up.
    In GNOME 3.8, not only does it insist that these windows are always started as small little bunched-up windows that I need to resize, but every time a window displays a notification/warning (message in internal yellow bar inside the window - such as loss of internet connection, mail retrieval failure etc) it resizes the windows spontaneously to a stupid, small size that overlays the other windows. This is driving me crazy!
    Where can I learn a bit more about how window sizing / positioning works in GNOME 3.8, or is it finally time to switch to awesome wm? I want to love GNOME 3.8, I really do. It's so slick, but so... unpolished.
    I want to dig in an assist with problems like these, but I need some pointers to some background material first to understand the problem. Is it the window manager? Is it the app?
    ** UPDATE: Doing a full system upgrade, as of May 18, 2013, has resolved this annoying problem. My windows now stay where they belong, and start with the same size they were closed with. GNOME is now pleasant to use again :-)
    Last edited by dawid.loubser (2013-05-21 13:37:25)

    dawid.loubser wrote:Thanks for the suggestion drtebi - I'll give it a try.
    I really like GNOME 3.x though (and would like to understand the windowing behaviour), but if the annoying quirks are insurmountable, I will happily switch.
    Man I love GNOME 3.x. I admire the courage they had to change, basically, everything, and I find myself more productive with my GNOME 3 Arch box than with my good ol' Slackware KDE 4 box. I just hate those bugs - for example I filed a task in their bugtracker for this window resize problem I have with gedit. If it's a love/hate relationship, I think it's marriage ^_^
    With the 3.8 upgrade, deadbeef was having a similar problem with window size/position. I just recompiled it against the latest GTK+3 package upgrade (that came after the 'big upgrade' here on Arch) and it was fixed. But not with gedit
    bwat47 wrote:
    Man I really hope this gets fixed soon, because aside from this one incredibly annoying issue I am loving gnome 3.8.
    I get the feeling gnome badly needs more beta testers, sizable regressions like this in "stable" releases happen way too often sad.
    I get the exact same feeling. Well bugs exist everywhere, there's no denying. But I think it would be wiser to 'alternate' the nature of each major stable release - one focusing on new features and one focusing on fixing bugs. For example if the only new features in GNOME 3.10 were the AppsFolder full implementation and the introduction of gnome-calendar, and the rest of the development cicle being devoted to fix bugs, I'd be more than happy.
    Like Fedora and Ubuntu, the fixed 6-month release cycle colaborates with the bugs. They don't do like Debian or Slackware which are released 'when they are ready'.
    EDIT: fout (yet) another bug. At least with facebook chat (haven't tested with other telepathy plugins) the buddy tray icon appear duplicate. Anybody with the same issue?
    Last edited by lmello (2013-05-02 14:06:06)

  • I am using Firefox 3.6.8. Oddly, my problem appeared a few hours PRIOR to Firefox automatically installing the latest updates (the week ending 7/23), not afterwards. The problem is this: the browser continues to display tabs, the reload/home/history/favor

    I am using Firefox 3.6.8. Oddly, my problem appeared a few hours PRIOR to Firefox automatically installing the latest updates (the week ending 7/23), not afterwards. The problem is this: the browser continues to display tabs, the reload/home/history/favorites icons, URL field and Google search field while in full-screen mode, so it's not really full-screen anymore. How can I correct this?
    == This happened ==
    Every time Firefox opened
    == Oddly, my problem appeared a few hours PRIOR to Firefox automatically installing the latest updates (the week ending 7/23), not afterwards.

    Do you have that problem when running in the Firefox SafeMode?
    [http://support.mozilla.com/en-US/kb/Safe+Mode]
    ''Don't select anything right now, just use "Continue in SafeMode."''
    If not, see this:
    [http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes]

  • How to solve illustrator cs6 save as cs5 problem about the stroke(when the stroke with clipping mask and color is gradient, save as cs5 will change to embed ).

    how to solve illustrator cs6 save as cs5 problem about the stroke(when the stroke with clipping mask and color is gradient, save as cs5 will change to embed ).

    Because it was not possible to apply a gradient to a stroke in CS5. When you open the file in CS5, it is reduced to something that can be rendered in CS5.

  • Preview Application Resizing Problem

    Preview Application Resizing Problem
    Microsoft platforms have two significant advantages. The first is the concept of an operating system that can function with hardware that ranges from cellular phones to desktop computers. The second is that Microsoft has excellent software development tools
    for creating and testing computer programs.
    Software compatibility across hardware platforms requires not only meeting CPU and memory requirements. Application programs must be able to automatically adjust Window and control sizes to meet the needs of available window sizes, video display unit sizes
    and screen resolutions, switching between vertical and horizontal viewing, vertical and horizontal scrolling, changes in font sizes , and variations in the available screen space due to usage of vertical and horizontal toolbars.
     Software developers must be careful that resizing doesn’t squeeze controls too close together or make them so small that they cannot be finger or stylus selected when used with touch screens.
    Some of the required automatic resizing options are provided by the Microsoft software compilers and the Windows operating system.  Softgroup Component’s “.NET  Forms Resize” is an example of one of the third party applications that provide advanced
    resizing functionality.
    Many of the resizing functions are programmer options and, if not properly enabled, an application may not have the required resizing functionality. At the current state of the art, application programs are highly variable in their capability to do the “intelligent
    resizing” that is required to handle different display environments.
    A case in point is the Microsoft Preview Application for Windows 10. When entering lengthy comments, the send button becomes positioned off the end of the program window. It is possible to scroll to the button, but the display automatically resets when scroll
    is released. The result is that the text cannot be sent. You can try a "blind" TAB to the SEND button. This appeared to work after several tries, but the comment was apparently not received,
    RERThird

    Hi,
    What do you see when you open the same PDF file in Acrobat Reader? Are the words still squeezed than?
    Dimaxum

  • Help me for solve this Question this is my problem

    help me for solve this Question this is my problem
    i installed EBS 11i fresh not vision
    i did cart of account and did set of book
    then assigned it with profile option gl set of books name
    and when enter to make ajournal appeare this messege
    [http://www9.0zz0.com/2009/10/06/03/232202588.jpg]
    [http://www9.0zz0.com/2009/10/06/03/634050066.jpg]

    Hi,
    Not sure why are you getting this kind of error (which is pointing to a URL with Jpg file) while creating a journal.
    Could you please bounce your server once and try..
    Please let us know if the error/warning stopping you to enter a journal in GL??
    We don't think profile option is a show stopper here.... We assume that you have assigned Sets of Books, MO: Operating unit & HR USer Profile option at Responsibility level correctly....
    Regards,
    S.P DASH

  • Illustrator Resizing Problems

    I am having reduction resizing problems in Illustrator CS6.  E.G. Straws & lemon wedge rinds become significantly proportionately wider when reduced.   Also, numerical text does not skew with everything else.  I have a CC membership w/PS & Ai installed.  There are no other Adobe items on my 8 month old imac, Lion 10.7.4 except Flash player & the Adobe Applications Manager.  Additionally, I have no 3rd party plug-ins & deleting the prefs file does not fix the problem.  Any help on this matter would be greatly appreciated. 

    sgem,
    And untick Align to Pixel Grid if ticked (you can do it in the Transform panel, or search for it in the Helpfile).
    Hi Steve. Still summer?

  • Odd Overheating Problem w/ Neo4-F

    I just recently got all the parts for my girlfriend's birthday present but I'm having an odd overheating problem that is only happening on the CPU.
    MSI Neo4-F
    AMD 64 3200+ Venice w/ stock HSF and thermal grease
    Geforce 6800GS
    Thermaltake Soprano case
    Thermaltake 430w PSU
    2GB Corsair Value DDR ram
    Seagate 160gb SATAII HDD
    Windows XP Home
    I built the PC no problem, hooked it up, it POSTs on the first try.  I install and update Windows, install drivers, DirectX, and install City of Villains to see how it runs.  It looks great, no stuttering, but after couple of minutes the PC just turns off.  I turn it back on, go into the BIOS, and the CPU temp is in the high 40s.  I download Prime95 and Core Center to check out the temps during load.
    My CPU temp goes up about 1C/second until it slows down before 60C, and when it finally reaches 60C, it shuts down.  All other sensors stay in the 30s.  I put my hand up to the HSF after the shutdown and it was barely warm.  I can barely feel any heat in the entire case.
    I flashed the BIOS to the latest, no luck, it doesn't help.  I reseat the HSF, doesn't help.  Tried different Cool 'n Quiet, no change.  I'm out of ideas.  Does anyone know what it might be?

    Quote from: MurdoK on 13-January-06, 17:39:24
    Hello !!
    Try the following:
    Doublecheck if your Heatsink sits properly on the Cpu and the thermal grease is applied correctly. Otherwise you could fry you CPU.
    Plug out Power Cable from PSU, and push Power On Button for 5sec. The Power On Led should light up.Open PC Case, then replug Power Cable and start the PC. Go into Bios Setup and search under PC Health Options for "Cpu Temperature Shutdown". Set it to the highest possible value.
    Check again if you have such high temps. If your Heatsink doesn´t get warm, but the CPU does, this is an indication for poor thermal heat transfer from CPU to Heatsink 
    Greetz MurdoK
    I see no option in my BIOS to up the CPU Temp Shutdown.  I don't know why the thermal grease would be applied incorrectly, the square of it on the HSF didn't get touched before landing ontop of the CPU.  I also removed and reseated the HSF to make sure it was on correctly.
    Quote from: Stick on 13-January-06, 18:07:21
    check if you have removed the plastic cover from the bottom of the HSF. happened before 
    Definitely got the plastic off.

  • DV resize problem with QuickTime's iPod 320 x 240 export

    Just a heads up for those with new 5th generation iPods who plan on converting their DV movies for display on the iPod. It seems that the iPod 320 x 240 export does not resize DV correctly. Here is a link concerning this problem:
    Waymen, "Possible resize problem with iPod 320 x 240 Export?" #1, 03:02am Oct 13, 2005 CDT

    This article show a workaround to have DV export correctly in QuickTime Pro
    http://docs.info.apple.com/article.html?artnum=302955

  • [Solved]XFCE 4.8 - Odd problem with terminal size.

    I've been using Xfce for nearly two months now, and am enjoying it quite a bit.   However last night an odd, and annoying, problem cropped up that I can't seem to figure out.
    For the main font I'm using Sans.   If I set it to 9 (which is what I would like as default size) it makes my terminal emulators open with 70x21 instead of 80x24.   When I check out ~/.config/Terminal/terminalrc, it still has 80x24 as its settings.   I use Terminator as my main terminal emulator, and its config contains no geometry settings at all.   I also checked out Xterm's config just to be sure, and even it is still set to 80x24.   
    If I set the font size to 10+, the terminal behaves correctly again.   I've narrowed down all possible config files, and the only thing I see changing the terminal size is when I move the font size down to 9. 
    I suppose i could create a bash script to launch terminator with the -geometry=80x24 string, but that just seems sloppy.
    Last edited by Beelzebud (2011-06-07 17:29:19)

    I found a solution to my problem.   I'm using the Oxygen-Gtk theme, which mimics the KDE4 oxygen theme.   In the theme is a config file called 'kdeglobals', which contains font settings.  If I set the 'desktopFont' and 'font' settings to 10, and leave the 'menuFont' at 9, it actually achieves a result better than I was hoping for.   My menus and UI all have small fonts now, but the fonts inside of the windows (like medit or thunar) are at 10 which are a bit easier to read.  I'm still not sure why setting the default font to 9 causes the terminal window to shrink, but this ended up working better than I had planned.  I guess I should have tinkered a bit more before I posted.   I just needed to sleep on it.   
    At any rate I'm happy now.   I have a very sleek looking dark oxygen theme on xfce4.
    Just so this wasn't a complete waste of everyone's time, here are the config files I'm using to achieve a dark oxygen-gtk theme.   Just install oxygen-gtk, and then make a copy of /usr/share/themes/oxygen-gtk and use these configs for a darker look:
    /usr/share/themes/oxygen-gtk-dark/gtk-2.0/kdeglobals
    [ColorEffects:Disabled]
    Color=112,111,110
    ColorAmount=-0.8
    ColorEffect=0
    ContrastAmount=0.65
    ContrastEffect=1
    IntensityAmount=0.25
    IntensityEffect=2
    [ColorEffects:Inactive]
    ChangeSelectionColor=true
    Color=0,0,0
    ColorAmount=0.025
    ColorEffect=2
    ContrastAmount=0.4
    ContrastEffect=2
    Enable=false
    IntensityAmount=0
    IntensityEffect=0
    [Colors:Button]
    BackgroundAlternate=66,65,64
    BackgroundNormal=64,63,62
    DecorationFocus=39,94,160
    DecorationHover=87,129,176
    ForegroundActive=150,191,240
    ForegroundInactive=120,119,117
    ForegroundLink=80,142,216
    ForegroundNegative=232,88,72
    ForegroundNeutral=192,162,95
    ForegroundNormal=232,230,227
    ForegroundPositive=120,183,83
    ForegroundVisited=142,121,165
    [Colors:Selection]
    BackgroundAlternate=22,68,120
    BackgroundNormal=24,72,128
    DecorationFocus=39,94,160
    DecorationHover=87,129,176
    ForegroundActive=150,191,240
    ForegroundInactive=81,119,166
    ForegroundLink=80,142,216
    ForegroundNegative=232,88,72
    ForegroundNeutral=192,162,95
    ForegroundNormal=255,255,255
    ForegroundPositive=120,183,83
    ForegroundVisited=142,121,165
    [Colors:Tooltip]
    BackgroundAlternate=17,51,86
    BackgroundNormal=16,48,80
    DecorationFocus=39,94,160
    DecorationHover=87,129,176
    ForegroundActive=150,191,240
    ForegroundInactive=120,119,117
    ForegroundLink=80,142,216
    ForegroundNegative=232,88,72
    ForegroundNeutral=192,162,95
    ForegroundNormal=196,209,224
    ForegroundPositive=120,183,83
    ForegroundVisited=142,121,165
    [Colors:View]
    BackgroundAlternate=36,35,35
    BackgroundNormal=32,31,31
    DecorationFocus=39,94,160
    DecorationHover=87,129,176
    ForegroundActive=150,191,240
    ForegroundInactive=120,119,117
    ForegroundLink=80,142,216
    ForegroundNegative=232,88,72
    ForegroundNeutral=192,162,95
    ForegroundNormal=212,210,207
    ForegroundPositive=120,183,83
    ForegroundVisited=142,121,165
    [Colors:Window]
    BackgroundAlternate=52,51,50
    BackgroundNormal=48,47,47
    DecorationFocus=39,94,160
    DecorationHover=87,129,176
    ForegroundActive=150,191,240
    ForegroundInactive=120,119,117
    ForegroundLink=80,142,216
    ForegroundNegative=232,88,72
    ForegroundNeutral=192,162,95
    ForegroundNormal=224,222,219
    ForegroundPositive=120,183,83
    ForegroundVisited=142,121,165
    [General]
    XftAntialias=true
    XftHintStyle=hintmedium
    XftSubPixel=none
    desktopFont=Sans Serif,10,-1,5,50,0,0,0,0,0
    fixed=Monospace,9,-1,5,50,0,0,0,0,0
    font=Sans Serif,10,-1,5,50,0,0,0,0,0
    menuFont=Sans Serif,9,-1,5,50,0,0,0,0,0
    shadeSortColumn=true
    smallestReadableFont=Sans Serif,8,-1,5,50,0,0,0,0,0
    taskbarFont=JH_Fallout,9,-1,5,50,0,0,0,0,0
    toolBarFont=Sans Serif,8,-1,5,50,0,0,0,0,0
    [Icons]
    Theme=Amazing_Dark
    *Change the icon theme to whatever you want
    /usr/share/themes/oxygen-gtk-dark/gtk-2.0/
    # global settings
    gtk-alternative-button-order = 1
    # oxygen's generic style options
    style "oxygen-default"
    GtkPaned::handle-size = 3
    GtkButton::child_displacement_x = 0
    GtkButton::child_displacement_y = 0
    GtkButton::default_border = { 0, 0, 0, 0 }
    GtkButton::default_outside_border = { 0, 0, 0, 0 }
    GtkButton::inner-border = { 2, 2, 1, 0 }
    GtkToggleButton::inner-border = { 0, 0, 1, 0 }
    GtkCalendar::inner-border = 0
    GtkCalendar::horizontal-separation = 0
    GtkCheckButton::indicator-size = 18
    GtkComboBox::appears-as-list = 1
    GtkEntry::honors-transparent-bg-hint = 1
    GtkExpander::expander-size = 15
    GtkMenu::horizontal-padding = 3
    GtkMenu::vertical-padding = 5
    GtkMenu::horizontal-offset = -7
    GtkCheckMenuItem::indicator-size = 16
    GtkScale::slider-width = 23
    GtkScale::slider-length = 15
    GtkScrollbar::trough-border=1
    GtkScrollbar::stepper-size=12
    GtkScrolledWindow::scrollbar-spacing=1
    GtkStatusbar::has-resize-grip = FALSE
    GtkTreeView::allow-rules = 1
    GtkTreeView::row-ending-details = 1
    GtkTreeView::expander-size = 15
    # shadow types
    GtkMenuBar::shadow-type = GTK_SHADOW_NONE
    GtkStatusbar::shadow-type = GTK_SHADOW_NONE
    GtkToolbar::shadow-type = GTK_SHADOW_NONE
    bg[NORMAL] = { 0.188, 0.184, 0.184 }
    bg[SELECTED] = { 0.094, 0.282, 0.502 }
    bg[INSENSITIVE] = { 0.188, 0.184, 0.184 }
    bg[ACTIVE] = { 0.165, 0.161, 0.161 }
    bg[PRELIGHT] = { 0.188, 0.184, 0.184 }
    base[NORMAL] = { 0.125, 0.122, 0.122 }
    base[SELECTED] = { 0.094, 0.282, 0.502 }
    base[INSENSITIVE] = { 0.188, 0.184, 0.184 }
    base[ACTIVE] = { 0.094, 0.282, 0.502 }
    base[PRELIGHT] = { 0.094, 0.282, 0.502 }
    text[NORMAL] = { 0.831, 0.824, 0.812 }
    text[SELECTED] = { 1.000, 1.000, 1.000 }
    text[INSENSITIVE] = { 0.165, 0.161, 0.161 }
    text[ACTIVE] = { 1.000, 1.000, 1.000 }
    text[PRELIGHT] = { 1.000, 1.000, 1.000 }
    fg[NORMAL] = { 0.878, 0.871, 0.859 }
    fg[SELECTED] = { 1.000, 1.000, 1.000 }
    fg[INSENSITIVE] = { 0.165, 0.161, 0.161 }
    fg[ACTIVE] = { 0.878, 0.871, 0.859 }
    fg[PRELIGHT] = { 0.878, 0.871, 0.859 }
    engine "oxygen-gtk"
    class "*" style "oxygen-default"
    # entries
    # do not change unless also changing Entry_SideMargin in OxygenStyle.h
    style "oxygen-entry-margins" = "oxygen-default"
    { xthickness = 5 }
    class "GtkEntry" style "oxygen-entry-margins"
    # menuitems padding
    style "oxygen-menubar" = "oxygen-default"
    xthickness = 1
    ythickness = 1
    class "GtkMenuBar" style "oxygen-menubar"
    # menuitems padding
    style "oxygen-menubaritem" = "oxygen-default"
    { xthickness = 3 }
    style "oxygen-menuitem" = "oxygen-default"
    xthickness = 1
    ythickness = 5
    style "oxygen-separator-menuitem" = "oxygen-default"
    xthickness = 1
    ythickness = 1
    class "GtkMenuItem" style "oxygen-menubaritem"
    widget_class "*<GtkMenu>.<GtkMenuItem>" style "oxygen-menuitem"
    widget_class "*<GtkMenu>.<GtkSeparatorMenuItem>" style "oxygen-separator-menuitem"
    # toolbuttons with menu
    style "oxygen-menutoolbutton" = "oxygen-default"
    xthickness=1
    ythickness=1
    GtkButton::focus-padding=0
    GtkWidget::focus-line-width=0
    class "*GtkMenuToolButton" style "oxygen-menutoolbutton"
    widget_class "*.GtkMenuToolButton.*Box.GtkToggleButton" style "oxygen-menutoolbutton"
    # icon views
    style "oxygen-iconview" = "oxygen-default"
    { GtkWidget::focus-line-width=0 }
    class "GtkIconView" style "oxygen-iconview"
    # notebook settings
    style "oxygen-notebook" = "oxygen-default"
    xthickness = 4
    ythickness = 4
    class "GtkNotebook" style "oxygen-notebook"
    # comboboxes
    style "oxygen-combobox" = "oxygen-default"
    # must set combobox frame x thickness to 0, otherwise there
    # is a dead area between combobox text and button
    xthickness = 0
    style "oxygen-combobox-frame" = "oxygen-default"
    # must set combobox frame x thickness to 0, otherwise there
    # is a dead area between combobox text and button
    xthickness = 4
    ythickness = 4
    class "GtkComboBox" style "oxygen-combobox"
    widget_class "*<GtkComboBox>.<GtkFrame>" style "oxygen-combobox-frame"
    # editable combobox margins
    style "oxygen-combobox-entry" = "oxygen-default"
    xthickness = 1
    ythickness = 1
    class "GtkComboBoxEntry" style "oxygen-combobox-entry"
    style "oxygen-combobox-entry-button" = "oxygen-combobox-entry"
    { xthickness = 2 }
    widget_class "*<GtkComboBoxEntry>.<GtkButton>" style "oxygen-combobox-entry-button"
    style "oxygen-combo-button" = "oxygen-combobox-entry"
    { xthickness = 0 }
    widget_class "*<GtkCombo>.<GtkButton>" style "oxygen-combo-button"
    # option menu
    style "oxygen-option-menu" = "oxygen-default"
    xthickness = 4
    ythickness = 0
    class "GtkOptionMenu" style "oxygen-option-menu"
    # vertical separators need enough room
    style "oxygen-vseparator" = "oxygen-default"
    { xthickness = 3 }
    class "GtkVSeparator" style "oxygen-vseparator"
    # 2pixels thickness.
    style "oxygen-w2" = "oxygen-default"
    xthickness = 2
    ythickness = 2
    class "GtkScrolledWindow" style "oxygen-w2"
    class "GtkViewport" style "oxygen-w2"
    class "GtkFrame" style "oxygen-w2"
    class "GtkProgressBar" style "oxygen-w2"
    # tree headers
    style "oxygen-header" = "oxygen-default"
    xthickness = 2
    ythickness = 0
    widget_class "*<GtkTreeView>.<GtkButton>" style "oxygen-header"
    widget_class "*<GtkList>.<GtkButton>" style "oxygen-header"
    widget_class "*GimpThumbBox*.<GtkEventBox>.<GtkVBox>.<GtkButton>" style "oxygen-header"
    # Workarounds
    # gimp
    style "oxygen-gimp-scale"
    # this ensures that toolpanels fonts in gimp is identical
    # to default font (which otherwise is ugly
    GimpDock::font-scale = 1.01
    class "*" style "oxygen-gimp-scale"
    This will basically give you an oxygen theme in gtk2 that looks nearly identical to KDE4's Oxygen theme with the Obsidian Coast color pack.

  • [SOLVED] openbox problem

    hi,
    i have 2 x screens, but cant get openbox on both at the same time! i looked at the faq in the openbox wiki, but it wasn;t much help;
    How do I run Openbox across multiple X screens?
    In order to have Openbox manage multiple X screens (this is not the same as multi-monitor TwinView or Xinerama), you need to run an instance of Openbox directly on each screen. We've put work into making Openbox work well with other instances of itself, for this type of configuration.
    In order to run Openbox on two screens, use commands such as these:
    # run openbox on the second screen (they start from 0)
    DISPLAY=:0.1 openbox
    # by default openbox will run on the first screen (screen number 0)
    exec openbox-session
    i assumed that after reading this, all i need to do is put the following into my ~/.xinitrc
    DISPLAY=:0.0 openbox
    DISPLAY=:0.1 openbox
    or
    DISPLAY=:0.1 openbox
    but neither worked! what have i missed?
    Last edited by ninjaprawn (2008-12-16 20:36:14)

    ok, after re-reading all the advice, i think you have all missed the point of what i am trying to achieve!
    fluxbox, kde, gnome & xfce all achieve this 'out of the box', openbox & icewm dont!!
    i am now concentrating on openbox. i currently have my pc looking & running perfectly, but i cant fire up vlc on my tv! I have a gforce 6200 with crt connection going to a 17" crt, & a tv-out going to a 28" tv!!
    my xorg.conf
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" RightOf "Screen0"
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "xtrap"
    Load "extmod"
    Load "record"
    Load "dbe"
    Load "glx"
    Load "freetype"
    EndSection
    Section "ServerFlags"
    Option "Xinerama" "0"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbModel" "logiaccess"
    Option "XkbLayout" "gb"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "NCI NEC CI A727"
    HorizSync 30.0 - 70.0
    VertRefresh 50.0 - 150.0
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "TV-0"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "NV44A [GeForce 6200]"
    Option "MigrationHeuristic" "greedy"
    Option "RenderAccel" "true"
    Option "AllowGLXWithComposite" "true"
    EndSection
    Section "Device"
    Identifier "Videocard0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 6200"
    BusID "PCI:1:0:0"
    Screen 0
    Option "MigrationHeuristic" "greedy"
    Option "RenderAccel" "true"
    Option "AllowGLXWithComposite" "true"
    EndSection
    Section "Device"
    Identifier "Videocard1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 6200"
    BusID "PCI:1:0:0"
    Screen 1
    Option "MigrationHeuristic" "greedy"
    Option "RenderAccel" "true"
    Option "AllowGLXWithComposite" "true"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Videocard0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "AddARGBGLXVisuals" "True"
    Option "DisableGLXRootClipping" "True"
    Option "TwinView" "0"
    Option "TwinViewXineramaInfoOrder" "CRT-0"
    Option "metamodes" "CRT: nvidia-auto-select +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Videocard1"
    Monitor "Monitor1"
    DefaultDepth 24
    Option "AddARGBGLXVisuals" "True"
    Option "DisableGLXRootClipping" "True"
    Option "TwinView" "0"
    Option "metamodes" "TV: 640x400 +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Section "Extensions"
    Option "Composite" "Enable"
    Option "RENDER" "Enable"
    EndSection
    however, openbox does absolutely nothng with the second screen! x fires up fine on it, but there is no openbox. the way fluxbox achieves this is with its config script having parameters for multiple screens;
    session.screen0.tab.placement: TopLeft
    session.screen0.tab.width: 64
    session.screen0.tab.height: 16
    session.screen0.menu.alpha: 150
    session.screen0.tabs.maxOver: false
    session.screen0.tabs.intitlebar: true
    session.screen0.tabs.usePixmap: false
    session.screen0.toolbar.tools: prevworkspace, nextworkspace, iconbar, systemtray, clock
    session.screen0.toolbar.onTop: False
    session.screen0.toolbar.maxOver: false
    session.screen0.toolbar.alpha: 224
    session.screen0.toolbar.visible: true
    session.screen0.toolbar.widthPercent: 86
    session.screen0.toolbar.layer: Dock
    session.screen0.toolbar.autoHide: false
    session.screen0.toolbar.placement: BottomCenter
    session.screen0.toolbar.height: 0
    session.screen0.toolbar.onhead: 0
    session.screen0.titlebar.left: Stick
    session.screen0.titlebar.right: Minimize Maximize Close
    session.screen0.clientMenu.usePixmap: true
    session.screen0.window.focus.alpha: 168
    session.screen0.window.unfocus.alpha: 150
    session.screen0.iconbar.iconWidth: 140
    session.screen0.iconbar.alignment: Left
    session.screen0.iconbar.wheelMode: Screen
    session.screen0.iconbar.mode: {static groups}
    session.screen0.iconbar.iconTextPadding: 40l
    session.screen0.iconbar.usePixmap: true
    session.screen0.overlay.lineWidth: 1
    session.screen0.overlay.lineStyle: LineSolid
    session.screen0.overlay.joinStyle: JoinMiter
    session.screen0.overlay.capStyle: CapNotLast
    session.screen0.slit.onTop: False
    session.screen0.slit.acceptKdeDockapps: true
    session.screen0.slit.maxOver: false
    session.screen0.slit.alpha: 255
    session.screen0.slit.direction: Vertical
    session.screen0.slit.autoHide: false
    session.screen0.slit.layer: Desktop
    session.screen0.slit.onhead: 0
    session.screen0.slit.placement: LeftBottom
    session.screen0.menuMode: Delay
    session.screen0.colPlacementDirection: TopToBottom
    session.screen0.windowScrollAction:
    session.screen0.showwindowposition: false
    session.screen0.defaultDeco: NORMAL
    session.screen0.noFocusWhileTypingDelay: 0l
    session.screen0.decorateTransient: true
    session.screen0.workspaceNames: Page 1,Page 2,three,four,
    session.screen0.fullMaximization: false
    session.screen0.workspacewarping: false
    session.screen0.allowRemoteActions: false
    session.screen0.userFollowModel: Follow
    session.screen0.focusLastWindow: True
    session.screen0.rowPlacementDirection: LeftToRight
    session.screen0.menuDelayClose: 0
    session.screen0.followModel: Ignore
    session.screen0.menuDelay: 0
    session.screen0.windowPlacement: RowSmartPlacement
    session.screen0.reversewheeling: false
    session.screen0.focusNewWindows: true
    session.screen0.workspaces: 2
    session.screen0.opaqueMove: true
    session.screen0.clickRaises: true
    session.screen0.autoRaise: true
    session.screen0.maxIgnoreIncrement: true
    session.screen0.demandsAttentionTimeout: 500
    session.screen0.desktopwheeling: true
    session.screen0.edgeSnapThreshold: 5
    session.screen0.tooltipDelay: 500
    session.screen0.maxDisableResize: false
    session.screen0.windowScrollReverse: false
    session.screen0.focusModel: ClickFocus
    session.screen0.imageDither: false
    session.screen0.resizeMode: Bottom
    session.screen0.tabFocusModel: ClickToTabFocus
    session.screen0.windowMenu:
    session.screen0.strftimeFormat: | %k:%M | %a - %e / %m / 20%y
    session.screen0.rootCommand: fbsetbg #/wallpaper/night.jpg
    session.screen0.maxDisableMove: false
    session.screen1.tab.placement: TopLeft
    session.screen1.tab.width: 64
    session.screen1.menu.alpha: 150
    session.screen1.tabs.maxOver: false
    session.screen1.tabs.intitlebar: true
    session.screen1.tabs.usePixmap: true
    session.screen1.toolbar.tools: iconbar, systemtray, clock
    session.screen1.toolbar.maxOver: false
    session.screen1.toolbar.alpha: 40
    session.screen1.toolbar.visible: true
    session.screen1.toolbar.autoHide: true
    session.screen1.toolbar.layer: Normal
    session.screen1.toolbar.widthPercent: 65
    session.screen1.toolbar.placement: BottomCenter
    session.screen1.toolbar.height: 0
    session.screen1.toolbar.onhead: 0
    session.screen1.titlebar.left: Stick
    session.screen1.titlebar.right: Minimize Maximize Close
    session.screen1.clientMenu.usePixmap: true
    session.screen1.window.focus.alpha: 55
    session.screen1.window.unfocus.alpha: 40
    session.screen1.iconbar.iconWidth: 70
    session.screen1.iconbar.alignment: Relative
    session.screen1.iconbar.wheelMode: Screen
    session.screen1.iconbar.mode: Workspace
    session.screen1.iconbar.iconTextPadding: 10l
    session.screen1.iconbar.usePixmap: true
    session.screen1.overlay.lineWidth: 1
    session.screen1.overlay.lineStyle: LineSolid
    session.screen1.overlay.joinStyle: JoinMiter
    session.screen1.overlay.capStyle: CapNotLast
    session.screen1.slit.acceptKdeDockapps: true
    session.screen1.slit.layer: Dock
    session.screen1.slit.autoHide: false
    session.screen1.slit.alpha: 255
    session.screen1.slit.maxOver: false
    session.screen1.slit.placement: BottomRight
    session.screen1.slit.onhead: 0
    session.screen1.slit.direction: Vertical
    session.screen1.menuMode: Delay
    session.screen1.colPlacementDirection: TopToBottom
    session.screen1.windowScrollAction:
    session.screen1.showwindowposition: true
    session.screen1.defaultDeco: NORMAL
    session.screen1.noFocusWhileTypingDelay: 0l
    session.screen1.decorateTransient: true
    session.screen1.workspaceNames: Workspace 2,Workspace 2,
    session.screen1.fullMaximization: false
    session.screen1.workspacewarping: true
    session.screen1.allowRemoteActions: false
    session.screen1.userFollowModel: Follow
    session.screen1.rowPlacementDirection: LeftToRight
    session.screen1.menuDelayClose: 0
    session.screen1.menuDelay: 0
    session.screen1.followModel: Ignore
    session.screen1.windowPlacement: RowSmartPlacement
    session.screen1.workspaces: 2
    session.screen1.reversewheeling: false
    session.screen1.focusNewWindows: true
    session.screen1.opaqueMove: false
    session.screen1.clickRaises: true
    session.screen1.autoRaise: true
    session.screen1.maxIgnoreIncrement: true
    session.screen1.desktopwheeling: true
    session.screen1.edgeSnapThreshold: 0
    session.screen1.tooltipDelay: 500
    session.screen1.maxDisableResize: false
    session.screen1.windowScrollReverse: false
    session.screen1.focusModel: ClickFocus
    session.screen1.imageDither: false
    session.screen1.resizeMode: Bottom
    session.screen1.tabFocusModel: ClickToTabFocus
    session.screen1.windowMenu:
    session.screen1.strftimeFormat: [%k:%M]-[%d/%m/%y]
    session.screen1.rootCommand: fbsetbg ~/wallpaper/night.jpg
    session.screen1.maxDisableMove: false
    session.styleOverlay: ~/.fluxbox/overlay
    session.cacheMax: 200l
    session.ignoreBorder: false
    session.menuFile: ~/.fluxbox/menu
    session.opaqueMove: False
    session.tabPadding: 0
    session.tabsAttachArea: Window
    session.groupFile: ~/.fluxbox/groups
    session.cacheLife: 5l
    session.autoRaiseDelay: 250
    session.slitlistFile: ~/.fluxbox/slitlist
    session.imageDither: True
    session.keyFile: ~/.fluxbox/keys
    session.modKey: Mod1
    session.styleFile: /home/danny/.fluxbox/styles/MacOSX
    session.forcePseudoTransparency: true
    session.doubleClickInterval: 250
    session.colorsPerChannel: 4
    session.configVersion: 10
    session.appsFile: ~/.fluxbox/apps
    as you can see, screen 0 is defined as well as screen 1!! is there a way of doing this in openbox??
    sorry for the long post!

  • [solved] Openbox keybind problem

    I am trying to bind windows+y key to display openbox menu, but it can't get it to work:
    <!-- Keybindings for running applications -->
    <keybind key="W-y">
    <action name="ShowMenu">
    <menu>root-menu</menu>
    </action>
    </keybind>
    <keybind key="W-e">
    <action name="Execute">
    <startupnotify>
    <enabled>true</enabled>
    <name>Konqueror</name>
    </startupnotify>
    <command>kfmclient openProfile filemanagement</command>
    </action>
    </keybind>
    The W-y keybind is being ignored, but W-e works fine.
    Last edited by Lockheed (2014-02-26 16:53:00)

    While swapping the binds I realised I was being stupid. I forgot my keyboard is German, but I am using US layout on it, so Y and Z are swapped. It's so natural for me that it is transparent to me while I type, but when I was binding the key, I was looking at the physical keys to pick the best candidate.
    Et voila...
    Thanks - your suggestion led me to realise it

  • Odd Display Problems - Solved (& More...)

    Earlier today I picked up the weird display problem shown in this thread: http://discussions.apple.com/thread.jspa?threadID=1524985&tstart=30
    I went ahead and reinstalled the Leopard Graphics Update and reset the PRAM. Problems seemed to go away. But then I ended up with an even weirder white-on-black display that looked a lot like an xray. So reset the PRAM again. No fix. Then restarted in SAFE mode - all OK, so probably not hardware. Then ran Disk Utility from the Leopard System CD. No probs revealed. Problem (white-on-black) came back on restart. Searched Discussion base and found reference to wrong toggle set in Universal Access System Preference. This was the white-on-black problem and toggling to black-on-white solved it.
    Here's the part I don't understand (but like): the machine is much faster than it was. Safari pages load with great speed, apps open faster, etc. It may have been the series of restarts that cleared something, but somewhere in this troubleshooting string things overall got a lot better. Beats me, but like it... YMMV.

    I just have some general thoughts. Does it look correct if you connect it to a different monitor? (to find out if the TV / TV connection is the problem) Did you install something in your house that could affect the signal that is being transmitted through the wire? (I highly doubt it) Are you SURE you didn't install / update / change any settings before it stopped working?
    The problem you described reminds me a little of the glitchy GTK problems I was having with my Radeon. My problem ended up being related to the open source driver and KMS. Is there another driver or video card you could try? Is your video card getting too hot?

  • [SOLVED] Openbox + fullscreen wine = focus problems

    Hi everyone,
    I've got this problem with Openbox: when i play a game via WINE (such as World of Warcraft or Guild Wars 2) in fullscreen, the screen become darker and unresponsive after a few mouse clicks. Then if I alt+tab twice, the wine screen become active again... until i decide to click again.
    If I play in non-fullscreen windowed mode, it somehow works (WoW and Hearthstone work but GW2 windows blinks dark for like 1 seconde everytime i click).
    If I use only the keyboard, everything's fine.
    If I set winecfg to create a virtual desktop, everything's fine too.
    If I use any other window managers (i tried with xfce, fluxbox, dwm...) i have no problem so i guess is something with the way Openbox and WINE interract.
    Any idea what this could be ?
    Last edited by Synchronyme (2014-05-31 07:18:34)

    Do you use a composition manager? Any application specific settings in rc.xml?
    Last edited by emeres (2014-05-30 17:54:40)

Maybe you are looking for