Fullscreen Firefox

2013-10-22 Thread Sean Goodwin
Hello,

I am currently using 3.5.1 on Gentoo linux and I am having a problem
fullscreen-ing (using Mod4 + f) Firefox, namely it doesn't work. What seems
to be happening is that it is engaging Firefox's fullscreen mode (hiding
the url bar) but not resizing the program to occupy the screen. It worked
properly at some point in the past, but stopped recently. I haven't changed
my rc.lua file and firefox does not have any custom rules set.

Any ideas?


Re: Align text in widget

2013-03-04 Thread Sean Goodwin
I seem to have found a way to do this, I'll post it here incase anyone
should have a similar issue.

Instead of using markup for the background I used:
http://awesome.naquadah.org/doc/api/modules/wibox.widget.background.html

Which I didn't know existed.


On Mon, Mar 4, 2013 at 7:34 PM, Sean Goodwin wrote:

> Hello,
>
> I'm currently running into a problem where text in a widget is not being
> aligned to the center of the wibox. Here is a picture:
>
> http://i.imgur.com/ORoUUYj.png
>
> As you can see the VOL widget text is lower than the SYS widget text. The
> problem seems to be occurring because I'm assigning two fonts to the
> textbox (I need to do this so the background color fills the entire area)
> like so:
>
> volume = '  color="#c8dfdf" font="Profont 8"> VOL:' .. volume
>
> Obviously I close the spans later.
>
> Anyone have any suggestions?
>


Re: visible attribute for wibox.widget objects in Awesome 3.5

2013-02-13 Thread Sean Goodwin
You might find this helpful.
http://thread.gmane.org/gmane.comp.window-managers.awesome/9659/focus=9662

On Mon, Feb 11, 2013 at 1:54 PM, Jacco  wrote:

> Hi,
>
> Today I ported my configuration to 3.5. I really like the changes, but I
> am missing a certain feature. Previously I could turn the visibility of
> a widget object on or off.
>
> example = widget({ type = "imagebox" })
> example.visible = false
>
> I have yet to find an equivalent. I turn the visibility of widgets on
> and off based on certain events, ie hide all mpd controls except play if
> mpd isn't playing or don't show up/down rates of network interfaces that
> aren't connect, this prevents my wiboxes from cluttering with pointless
> information.
>
> Short story: how to do this with wibox.widget objects? Specifically
> wibox.widget.imagebox and wibox.widget.textbox.
>
> Thanks for you help.
>
> Regards,
>
> Jacco
>
> --
> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>


Scaling Windows

2013-01-30 Thread Sean Goodwin
Hello,

I was wondering if it is possible to scale a floating window's size in
awesome by a certain percentage. For example, I could have a function that
shrinks the selected window by %50.


Get current tag from a screen

2013-01-28 Thread Sean Goodwin
Hello,

I'm trying to find a way to retrieve the current selected tag for a given
screen. If screen 1 was on tag 3, this function/whatever would return 3.
You get the idea. Is there anyway to do this?


Re: widgets and bottom wibox

2013-01-01 Thread Sean Goodwin
That's what I thought. You are using mywibox for both the top and the
bottom. You need to make a second one with a different name (unless I am
mistaken).

Outside of the loop declare a new variable (mywibox2 = {}). Then in the
loop, create the wibox.
mywibox2[s] = awful.wibox({ position = "bottom", screen = s }).

Then declare a new layout.
local layout2 = wibox.layout.align.horizontal()

Then add the sys widget (assuming that is all you want right now) to the
layout.
layout2:set_left(sys)

Finally, set the wibox's widget.
mywibox2[s]:set_widget(layout2)

That should work.


On Wed, Jan 2, 2013 at 1:19 AM, Shuuichi Nitori
wrote:

> well my top wibox is the default configuration that comes with awesome 3.5
> -- Create a promptbox for each screen
> mypromptbox[s] = awful.widget.prompt()
> -- Create an imagebox widget which will contains an icon indicating
> which layout we're using.
> -- We need one layoutbox per screen.
> mylayoutbox[s] = awful.widget.layoutbox(s)
> mylayoutbox[s]:buttons(awful.util.table.join(
>awful.button({ }, 1, function ()
> awful.layout.inc(layouts, 1) end),
>awful.button({ }, 3, function ()
> awful.layout.inc(layouts, -1) end),
>awful.button({ }, 4, function ()
> awful.layout.inc(layouts, 1) end),
>awful.button({ }, 5, function ()
> awful.layout.inc(layouts, -1) end)))
> -- Create a taglist widget
> mytaglist[s] = awful.widget.taglist(s,
> awful.widget.taglist.filter.all, mytaglist.buttons)
>
> -- Create a tasklist widget
> mytasklist[s] = awful.widget.tasklist(s,
> awful.widget.tasklist.filter.currenttags, mytasklist.buttons)
>
> -- Create the wibox
> mywibox[s] = awful.wibox({ position = "top", screen = s, height = 14 })
>
> -- Widgets that are aligned to the left
> local left_layout = wibox.layout.fixed.horizontal()
> left_layout:add(mylauncher)
> left_layout:add(mytaglist[s])
> left_layout:add(mypromptbox[s])
>
> -- Widgets that are aligned to the right
> local right_layout = wibox.layout.fixed.horizontal()
> if s == 1 then right_layout:add(wibox.widget.systray()) end
> right_layout:add(mytextclock)
> right_layout:add(mylayoutbox[s])
>
> -- Now bring it all together (with the tasklist in the middle)
> local layout = wibox.layout.align.horizontal()
> layout:set_left(left_layout)
> layout:set_middle(mytasklist[s])
> layout:set_right(right_layout)
>
> mywibox[s]:set_widget(layout)
>


Re: widgets and bottom wibox

2013-01-01 Thread Sean Goodwin
Could you post the code for the top wibox?

On Tue, Jan 1, 2013 at 4:55 PM, Shuuichi Nitori
wrote:

> hi again, I can't put some widgets on the wibox at bottom. it's annoying
> because all the widgets on the top wibox are also on the bottom wibox.
> thi is my bottom wibox:
>
> mywibox[s] = awful.wibox({ position = "bottom", screen = s , height = 14})
>
> and then, I try to put the *sys* widget:
>
>  local layout = wibox.layout.align.horizontal()
>  left_layout:add(sys)
>  layout:set_left(left_layout)
>  mywibox[s]:set_widget(layout)
>
> the *sys* widget appears, but also all the widgets on the top too
> (launcher, tasklist, clock, etc..)
> how can I separate the widgets on top and the widgets on bottom?
>
>


Re: Systray widget visibility

2012-12-31 Thread Sean Goodwin
Thanks for that, although it seems that once the I set the container's
widget to systray, setting it to nil again does not remove the systray from
my wibox. Any ideas? Do I have to have the wibox redraw itself or something?

On Mon, Dec 31, 2012 at 6:41 AM, Uli Schlachter  wrote:

> Hi,
>
> On 30.12.2012 22:43, Sean Goodwin wrote:
> > I upgraded to 3.5 today, and in the process of updating my widgets I
> > noticed something that seems to be missing, or at least I can't find it.
> In
> > 3.4 I could call visible on a systray (I.E. mst = widget({ type =
> "systray"
> > }), mst.visible = false and the systray would not show up) but now that
> > systrays are handled through wibox I can't seem to be able to set this
> > value. I've looked through the documentation to see if there was any
> > mention of a new visibility function, but I can't find anything. If
> anyone
> > could help me I would appreciate it.
>
> That's right, there is no ".visible" right now. Something like this could
> be
> added, if needed, to all widgets by implementing lots of magic in
> wibox.widget.base. However, I'm not sure if I really like this magic.
>
> In the mean time, here is some hack to fake .visible for any widget:
>
> local systray = wibox.widget.systray()
> local container = wibox.layout.margin(systray)
> (Use "container" instead of the actual systray in your wibox)
>
> To hide the systray:
>
> container:set_widget(nil)
>
> To make the systray visible:
>
> container:set_widget(systray)
>
> Uli
>
> --
> - Captain, I think I should tell you I've never
>   actually landed a starship before.
> - That's all right, Lieutenant, neither have I.
>
> --
> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>


Re: vertical orientation for default wibox

2012-12-31 Thread Sean Goodwin
Couple of ideas:
First, make sure you change the line where you declare the wiibox. It
should say "mywibox[s] = awful.wibox({ position = "top", screen = s })" by
default (I think). Change the position to left.
According to 
this
page,
vertical layouts have a top, bottom, and a middle. So instead of
left/right, you have top/bottom. If you change all of this it should work
(I didn't test it).

On Mon, Dec 31, 2012 at 11:33 AM, Prashanth  wrote:

>  Hi list,
> I use just the laptop monitor most of the time, which has a resolution of
> 1366x768. Vertical space is a premium, and so, up until 3.4.13, I had the
> default wibox oriented "left". I tried to do the same with the 3.5 release,
> and changed its 3 components to vertical:
>
> local left_layout = wibox.layout.fixed.horizontal() -- 1
> local right_layout = wibox.layout.fixed.horizontal() -- 2
> local layout = wibox.layout.align.horizontal() -- 3
>
>
> Making line 3 vertical crashes awesome completely -- I cannot even login
> after that. The function exists, so I don't see why it should crash like
> that.
>
> Has anyone else here been able to make the vertical status bar work in
> 3.5? Or can someone point me to a way of fixing it?
>
> Thanks!
> Prash
>


Systray widget visibility

2012-12-30 Thread Sean Goodwin
Hello,

I upgraded to 3.5 today, and in the process of updating my widgets I
noticed something that seems to be missing, or at least I can't find it. In
3.4 I could call visible on a systray (I.E. mst = widget({ type = "systray"
}), mst.visible = false and the systray would not show up) but now that
systrays are handled through wibox I can't seem to be able to set this
value. I've looked through the documentation to see if there was any
mention of a new visibility function, but I can't find anything. If anyone
could help me I would appreciate it.