lxappearance: the tab “Window border” is missing

Forum Forums General Software lxappearance: the tab “Window border” is missing

  • This topic has 4 replies, 2 voices, and was last updated Nov 28-2:49 am by madibi.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #29910
    Member
    madibi

      if I go in Control Centre –> Customize Look and Feel (= the same as to write the command lxappearance), what I have is the tool to change Themes, Icons, etc.
      Unfortunately I am searching to change the look in order to be similar to a Mac, and I don’t know how to change the border, due to the fact that in Antix this TAB is missing.
      Is it possible to change that detail with the cli? Or is it possible to add that tab?
      Many thx in advance for your help

      #29929
      Anonymous
        Helpful
        Up
        0
        ::

        antispam ate this post when I attempted to edit it.
        The post contained some incorrect details & needs further edit. I will followup in a separate post.

        • This reply was modified 3 years, 5 months ago by anticapitalista.
        #29930
        Anonymous
          Helpful
          Up
          0
          ::

          in lxappearance this TAB is missing

          lxappearance facilitates tweaking some details (but not window borders) of GTK themes.
          The tweaks applied via lxappearance only affect programs which employ a GTK ui.
          Also, separate Gtk2 and Gtk3 toolkits exist and Gtk3 theming engines will disregard some of the lxappearance-applied tweaks.


          post edited to a add:
          If you install the separate “lxappearance-obconf” package, lxappearance will display an additional tab, labeled “Window borders”, enabling your to tweak the borderWidth setting for OPENBOX window manager (which is not pre-installed in antiX and is probably not fully supported by the antiX “menu updater” utility.)

          Editing Gtk themes can be quite a chore.
          Each themeset may, or may not, provide both a Gtk2 and a Gtk3 theme variant. A theme which provides a Gtk3 variant may (or might not) further provide files containing declarations (rules) for 3.24, 3.22, 3.20 sub-variants. Instead of editing to separately customize each of the installed themes, we’re able to place overriding globally-applied select details (for gtk2 themes) within an ~/.gtkrc-2.0 or ~/.gtkrc.mine file… but if we a place similar “global” declaration file for Gtk3, the theme engine will regard the declarations as “all, or nothing” ~~ falling back to using specs from its default theme (Adwaita, or ClearLooks, depending on the theme engine) for any details we have not explicitly declared. Said differently: placing a global Gtk3 ini causes the theme engine to skip the step of considering (and parsing) the files provided by our currently-selected theme. This is why lxappearance cannot manage tweaks to Gtk3 theme variants. Below, I’ll describe what I believe is the least maddening, least hair-pulling, approach to cutomizing a Gtk2//Gtk3 themeset.

          Begin by copying a theme of interest, from
          /usr/share/themes/someHappyTheme
          to ~/.themes/someHappyTheme

          Optionally (I do recommend) websearch “customize gtk theme” and read several explanations of how the anklebone connects to the kneebone ~~ several, because the first few you read (skim) may not seem “aha” immediately clear.

          cd ~/.themes/someHappyTheme
          grep -inr ‘border’
          Understand that for Gtk3 variants, a given set of themefiles might contain zero declarations regarding border. If so, the theme author has deferred to allowing the theme engine to fallback and use whatever border specs are implicit to the theme engine’s default theme.
          .
          Within a themefile, you can either edit the lines containing any border-related declarations… or you can append your customizations to the foot of the file ~~ when the theme engine parses a file, it gives precedence to any REdeclared lines occurring lower within the file.
          .
          Gtk3 theme engines parse themefiles during session startup. After editing a Gtk3 theme, in order for the change to take effect you may need to fully logout from desktop session and reenter. YMMV, toggling a different theme then back to the recently-edited theme may (or may not) trigger a full reload of the themefiles.

          ____________________
          Separate from window borders applied via the gui toolkit (e.g. Gtk, Qt, wxWidgets) and theming engine employed by a given program, the window manager (e.g. IceWM, openbox, Xfwm) may provide ability to paint a border around all windows. Some provide a graphicky “look and feel” component ala lxappearance, others do not. The “how to specify use of wm-applied window borders” instructions differ for each of the window managers preinstalled in antiX,

          Using fluxbox, I would
          man fluxbox-styles (to jog my memory)
          then edit ~/.fluxbox/overlay and declare the following lines:
          window.borderColor: green
          window.borderWidth: 4

          then issue a fluxbox reconfigure or restart command to view the effect of the changes.

          #29950
          Member
          madibi
            Helpful
            Up
            0
            ::

            I start with a big THANK YOU for the time you gave me and the clear explanation.
            I’ll try to do something tonight and tomorrow, then I’ll give you my feed back.
            You clarified to me an area I had never approached and I didn’t even know which key words to use for google-research

          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.