Set opacity of widgets

  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/cimi/public_html/murrine/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/cimi/public_html/murrine/includes/theme.inc on line 170.
  • : Function ereg() is deprecated in /home/cimi/public_html/murrine/includes/file.inc on line 649.
  • : Function ereg() is deprecated in /home/cimi/public_html/murrine/includes/file.inc on line 649.
  • : Function ereg() is deprecated in /home/cimi/public_html/murrine/includes/file.inc on line 649.
  • : Function ereg() is deprecated in /home/cimi/public_html/murrine/includes/file.inc on line 649.
  • : Function ereg() is deprecated in /home/cimi/public_html/murrine/includes/file.inc on line 649.
  • : Function ereg() is deprecated in /home/cimi/public_html/murrine/includes/file.inc on line 649.
  • : Function ereg() is deprecated in /home/cimi/public_html/murrine/includes/file.inc on line 649.
  • : Function ereg() is deprecated in /home/cimi/public_html/murrine/includes/file.inc on line 649.
  • : Function ereg() is deprecated in /home/cimi/public_html/murrine/includes/file.inc on line 649.
  • : Function ereg() is deprecated in /home/cimi/public_html/murrine/includes/file.inc on line 649.
Your rating: None Average: 1 (6 votes)
I know this has been discussed somewhere, and IIRC you said “would be nice but not in the immediate plans”, but I figured we should have a request to track ;-) The request here is to be able to define opacity/alpha for each widget. By default, Murrine does close to the opposite of what I want; I want translucent menus and almost-transparent editors with opaque text. But I realise that's not what most want, so the best way to get what I want is by having opacity defined in the gtkrc.

I would not let the user

I would not let the user adjust the opacity level, but you can still disable RGBA in the gtkrc per-widget basis, just find out the widget you want to have opaque and add:
engine "murrine" { rgba = FALSE }

That can make my buttons

That can make my buttons opaque, but it won't make my editors translucent :-)

Yeah, a translucent editor

Yeah, a translucent editor is something totally strange, I would not go for it (you have to read the text, it must be opaque).

Yet, the most popular

Yet, the most popular translucent app is the terminal... how is that different?

I would also like to be able

I would also like to be able to define the widget opacity in the gtkrc. There are a few little things that I would like to make semi-transparent that are not.

I, myself, when I was

I, myself, when I was messing with rgba apps using an rgba module, changed some of the constants defining how opaque certain parts would be, the ones in support.h. Though of course, that meant recompiling murrine every time I made any kind of change. It also kills theme customizability. Everyone has to use the opacity levels you decided on, unless they recompile the engine. I imagine it would be a huge pain to allow opacity customizations on a per-widget basis. But you already use constants, which can be changed in the source easily enough... why not allow them to be changed in the gtkrc? What if some themer would like every widget in his theme to be opaque but menus and toolbars? What if some themer just wants the backs of his windows to be translucent? What about any other little tweaks, to make it as transucent as he sees fit? Right now, he'd have to distribute a modified version of murrine with his theme to accomplish it, which is far less than ideal. So why not change those constants you have in support.h so that they can be defined in the gtkrc?

I also vote for being able

I also vote for being able to set the opacity of widgets in gtkrc. I added rgba support to xfce-panel and you could image that I want my panel be more transparent than my other widgets. It would be very nice if we can configure that in gtkrc.

Why we cannot adjust the

Why we cannot adjust the opacity level?
WHY WHY WHY?

I too would also like to see

I too would also like to see the opacity options in gtkrc. Rebuild the engine every time you want to make an opacity change?? Puh-lease Murrine is definitely falling short of what it could be.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
  • Allowed HTML tags: <a> <b> <strong> <i> <em> <u> <br />

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions. Registered users are trusted and don't require this verification.
9 + 0 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.