headers
Zveroy | 1 Feb 2012 14:15
Picon

Re: Transparent systray background

> Is is possible to say something like:
> width = screenwidth-86

Yes, indeed. Just get necessary values from screen[s].workarea table
which have x, y, width and height properties. Use this peace of code
for example:

width = screen[s].workarea.width - TRAYER_HEIGHT * MAX_NUMBER_OF_ICONS

Don't forget replace TRAYER_HEIGHT and MAX_NUMBER_OF_ICONS with actual
values or vaiables. With multi-monitor configuration you will be
experiment a little to recognize right way of calculations.
Permalink | Reply | 1 comment |
headers
Marco | 1 Feb 2012 15:01

Re: Transparent systray background

On 2012-02-01 Zveroy <zveroy <at> gmail.com> wrote:

> > Is is possible to say something like:
> > width = screenwidth-86
> 
> Yes, indeed. Just get necessary values from screen[s].workarea table
> which have x, y, width and height properties. Use this peace of code
> for example:
> 
> width = screen[s].workarea.width - TRAYER_HEIGHT * MAX_NUMBER_OF_ICONS

Thanks for the snippet.

Marco
Permalink | Reply | 0 comments |
headers
Bearcat M. Sandor | 3 Feb 2012 00:09

transparency not working on terminals with certain colors, and suggested composting managers

Folks,

I'm a happy Awesome user, but i do miss my transparent windows from 
compiz days. To that end i have the following in my luarc:

awful.util.spawn_with_shell("xcompmgr -CcFf -t-5 -l-5 -r10.2 -o.55 -D3 
-I-.015 -O-.03 &")

under awful.rules.rules i have:

		{ rule = { class = "urxvt" },
       properties = { opacity = 0.8 } },

What i don't understand is that only the terminal with the background 
set to !URxvt*background: #3B3B3B is transparent and not the one set to 
URxvt*background:  #3f3f3f

Does xcompmgr only make darker colors transparent?

An image of this is at http://imgur.com/Fhxp5

I posted my lua.rc here: 
https://raw.github.com/gist/1726334/2cd8fb50315bacbafb841ceeef512dec1f90a5c2/rc.lua

Also, is there another compositing manager i can use with awesome? I 
don't think the compositing manager of compiz can be used by itself can 
it, and  the cairo composite manager project looks dead.

Thanks,
(Continue reading)

Permalink | Reply | 4 comments |
headers
Arnaud Fontaine | 3 Feb 2012 05:27
Favicon

Re: transparency not working on terminals with certain colors, and suggested composting managers

Hi,

"Bearcat M. Sandor" <linux <at> feline-soul.com> writes:

> I'm a  happy Awesome user, but  i do miss my  transparent windows from
> compiz days. To that end i have the following in my luarc:
>
> awful.util.spawn_with_shell("xcompmgr -CcFf -t-5 -l-5 -r10.2 -o.55 -D3
> -I-.015 -O-.03 &")
>
> under awful.rules.rules i have:
>
> 		{ rule =  { class = "urxvt" }, properties  = { opacity =
>       0.8 } },
>
> What i don't understand is that  only the terminal with the background
> set to !URxvt*background:  #3B3B3B is transparent and not  the one set
> to URxvt*background: #3f3f3f
>
> Does xcompmgr only make darker colors transparent?

xcompmgr only renders a  window as translucent if _NET_WM_WINDOW_OPACITY
property is set (you can check that this property is set with xprop) and
leave it to  the window manager or any other  tool (such as transset[0])
to set this property.

I'm not sure  why using properties does  not work there. Personally I use
different opacity value according to the focus status:

client.add_signal(
(Continue reading)

Permalink | Reply | 2 comments |
headers
Bearcat M. Sandor | 3 Feb 2012 06:38

Re: transparency not working on terminals with certain colors, and suggested composting managers

On 02/02/2012 09:27 PM, Arnaud Fontaine wrote:
> Hi,
>
> "Bearcat M. Sandor"<linux <at> feline-soul.com>  writes:
>
> xcompmgr only renders a  window as translucent if _NET_WM_WINDOW_OPACITY
> property is set (you can check that this property is set with xprop) and
> leave it to  the window manager or any other  tool (such as transset[0])
> to set this property.
>
> I'm not sure  why using properties does  not work there. Personally I use
> different opacity value according to the focus status:
>
> client.add_signal(
>      "focus",
>      function(c)
>         if c.class and (c.class:lower():find("rxvt") or c.class:lower():find("emacs")) then
>            c.opacity = 1.0
>         end
>      end)
>
> client.add_signal(
>      "unfocus",
>      function(c)
>         if c.class and (c.class:lower():find("rxvt") or c.class:lower():find("emacs")) then
>            c.opacity = 0.7
>         end
>      end)
>
Thanks Arnaud!  I'll try that based on focus and see how it does.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Arnaud Fontaine | 3 Feb 2012 07:43
Favicon

Re: transparency not working on terminals with certain colors, and suggested composting managers

Hi,

"Bearcat M. Sandor" <linux <at> feline-soul.com> writes:

> As  it happens  i  discovered Unagi  today and  installed  it Via  git
> source. It works well!  I did note that using synapse the entry box is
> not displaying properly with unagi  and it does display correctly with
> xcompmgr. If your  interested in more information on that  let me know
> of list and ill be glad to  provide you with screen shots and help you
> debug that.

Sure I'm always interested in fixing bugs in unagi ;-). You can submit a
bug report  at the following  URL with  as much information  as possible
(especially how I can reproduce it):

https://projects.mini-dweeb.org/projects/unagi/issues/new

Or we can also do it by email,  it's up to you. I personnally prefer the
bug tracker as I can keep track of it and not forget...

Regards,
--

-- 
Arnaud Fontaine
Permalink | Reply | 0 comments |
headers
Piotr Ozarowski | 3 Feb 2012 11:46
Picon
Gravatar

Re: transparency not working on terminals with certain colors, and suggested composting managers

[Bearcat M. Sandor, 2012-02-03]
> Does xcompmgr only make darker colors transparent?

for URxvt I prefer to set the transparency via ~/.Xdefaults:

| URxvt.background:	rgba:0000/0000/0000/efff
| URxvt.depth:		32

(remember to `xrdb ~/.Xdefaults` before opening new window)

BTW, my rc.lua contains:
| local set_opacity = function(client, value)
|     local v = client.opacity + value
|     if v >= 1 then
|         v = 1
|     elseif v < 0.1 then
|         v = 0.1
|     end
|     client.opacity = v
| end

and in clientkeys:
|     awful.key({ modkey, }, "Next", function (c) set_opacity(c, -0.1) end),
|     awful.key({ modkey, }, "Prior", function (c) set_opacity(c, 0.1) end)

so that I can use mod+PgUp/PgDown to change opacity in other windows

.oO(being able to use Python instead of Lua would make Awesome even more
    awesome)
--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Adrian C. | 4 Feb 2012 17:08

Re: awesome in Linux Action Show S04E20

Too bad they missed progressbars, ie. for the volume changer they 
complained about. It can be just as good looking, it reacts to scroll, 
and it can launch kmix/gmix/aumix/whatever.

--

-- 
Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618
PGP FP: 02A5 628A D8EE 2A93 996E  929F D5CB 31B7 D20A 0618
Permalink | Reply | 0 comments |
headers
Marco | 5 Feb 2012 12:08

Separator in menu

Dear list,

I'd like to draw a horizontal separator line in the menu to separate
groups of items? Is that possible? How?

Marco
Permalink | Reply | 2 comments |
headers
Alexander Yakushev | 5 Feb 2012 12:31
Picon
Gravatar

Re: Separator in menu

On 02/05/2012 01:08 PM, Marco wrote:
> Dear list,
>
> I'd like to draw a horizontal separator line in the menu to separate
> groups of items? Is that possible? How?
>
> Marco
Well, you can place an empty item, or an item filled with dashes. It 
will still be highlightable and clickable, thus that's kind of a crutch. 
But I saw many people doing this and I myself stick to this way.
Permalink | Reply | 1 comment |

Gmane