awesome | 2 Sep 22:27 2014

[awesome bugs] #1252 - Use a single icon for "maximized" (both vertical and horizontal)

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1252 - Use a single icon for "maximized" (both vertical and horizontal)
User who did this - Daniel Hahler (blueyed)

----------
This looks better: http://codepoints.net/U+1F542 (I've amended the PR).

(when submitting the comment with the symbol in it, flyspray crashed: Query {INSERT INTO
`flyspray_comments` (task_id, date_added, last_edited_time, user_id, comment_text) VALUES ( ?, ?,
?, ?, ? )} with params {1252,1409689584,1409689584,494,This looks better: [THEUNICODECHAR]
http://codepoints.net/U+1F542 (I've amended the PR).} Failed! (Incorrect string value:
'\xF0\x9F\x95\x82 h...' for column 'comment_text' at row 1))
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1252#comment4126

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 2 Sep 22:18 2014

[awesome bugs] #1252 - Use a single icon for "maximized" (both vertical and horizontal)

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1252 - Use a single icon for "maximized" (both vertical and horizontal)
User who did this - Daniel Hahler (blueyed)

----------
I have now used "⨣" (http://codepoints.net/U+2A23).

This might add a bit of confusion, because a "+" icon gets used in the taskbar to make a client "sticky", while
a square ("▪") is used to indicate sticky clients in the tasklist.

The PR is at https://github.com/awesomeWM/awesome/pull/44

A better codepoint might be found when searching for "cross": http://codepoints.net/search?q=&na=cross
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1252#comment4125

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 27 Aug 19:59 2014

[awesome bugs] #1295 - Menubar doesn't adapt width to different screen widths

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Sindre Føring Devik (tuusjr) 

Attached to Project - awesome
Summary - Menubar doesn't adapt width to different screen widths
Task Type - Bug Report
Category - Titlebars
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Normal
Reported Version - 3.5.5
Due in Version - Undecided
Due Date - Undecided
Details - The menubar sets the width of the menubar according to the width of the screen where it is first
opened, and then it assumes the same width wherever it is opened afterwards. For a multimonitor setup with
different screen widths, the menubar will either appear too long for the smaller screen or too small for
the bigger screen.

The fix would be to add a width check whenever the menubar is opened.

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1295

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
(Continue reading)

awesome | 25 Aug 07:09 2014

[awesome bugs] #1294 - over specified cflags

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Matthew Thode (prometheanfire) 

Attached to Project - awesome
Summary - over specified cflags
Task Type - Bug Report
Category - Build system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - over-specified cflags

We (gentoo) have noticed that there there is some over optimization being forced in the build and have
created a patch to remove the over specified flags.

https://bugs.gentoo.org/show_bug.cgi?id=509658

-O1 not needed (sometimes users specify diferently)
-ggdb3 used for debug info
-rdynamic also used for debug info

Let us know if you have questions or if there was a specific need for a flag.
(Continue reading)

awesome | 20 Aug 11:49 2014

[awesome bugs] #1293 - Systray won't show with margin layout

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#1293 - Systray won't show with margin layout
User who did this - Uli Schlachter (psychon)

Reason for closing: Fixed
Additional comments about closing: commit ac50f4b4121c84060bde9457d6cd3b02d6328271
Author: memeplex <carlosjosepita <at> gmail.com>
Date:   Mon Aug 18 02:32:11 2014 -0300

    Fix for FS#1293

    FS#1293 - Systray won't show with margin layout

    https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1293&project=1&order=dateopened&sort=desc

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1293

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 20 Aug 11:30 2014

[awesome bugs] #1293 - Systray won't show with margin layout

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1293 - Systray won't show with margin layout
User who did this - Uli Schlachter (psychon)

----------
Uhm. With that change, we will keep calling systray_register() on every redraw as long as the systray is
empty. That's not really a good thing....
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1293#comment4124

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 20 Aug 03:08 2014

[awesome bugs] #1230 - Yet another task-/taglist rewrite

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1230 - Yet another task-/taglist rewrite
User who did this - Emmanuel Lepage Vallee (Elv13)

----------
Drag and drop is easier to implement with the Radical implementation as it gives you the item under the
cursor once you drop the item with some wizardry. However, it is possible to subscribe to each mouse::move
events from the Radical taglist and it will give you the item under the cursor for each mouse events, the
item have a tag property with the tag. This is how I originally planned to implement the feature. However, I
never actually did it. Some of the low level code is there, but it is missing the high level drag and drop code
itself. Patches welcome (please avoid mousegrabber for this, not that it doesn't work, I id it before, but
you miss all the mouse::enter and mouse::leave signals that make implementing the feature much easier)

Radical:
https://github.com/Elv13/radical

Taglist usage:
https://github.com/Elv13/awesome-configs/blob/master/rc.lua#L375
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1230#comment4123

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

(Continue reading)

awesome | 19 Aug 21:30 2014

[awesome bugs] #1230 - Yet another task-/taglist rewrite

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1230 - Yet another task-/taglist rewrite
User who did this - Tomasz Rydzyński (qsorix)

----------
I'm not sure if it's covered by the plan. A use case I can think of is getting the tag under mouse, e.g. to
initiate drag&drop. It could be accomplished by having an easy way to get widget from tag, or tag from a
corresponding widget. Having this by default lets you do many things with tags using a mouse, without
resorting to a custom function creating widgets.

Here's my poor implementation of drag&drop reordering of tags in awesome 3.5
https://gist.github.com/qsorix/92269d2ea5bf8f205e97
I'd hope something like this would be much easier after the rewrite.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1230#comment4122

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 18 Aug 07:35 2014

[awesome bugs] #1293 - Systray won't show with margin layout

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1293 - Systray won't show with margin layout
User who did this - Carlos (memeplex)

----------
Pull request here:

https://github.com/awesomeWM/awesome/pull/42
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1293#comment4121

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 18 Aug 07:23 2014

[awesome bugs] #1293 - Systray won't show with margin layout

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1293 - Systray won't show with margin layout
User who did this - Carlos (memeplex)

----------
Well, I've found a cure. As the systray was never drawn it never got a chance to update and, by the same token,
to emit update events. This is because of the way systray.c is implemented and the way
capi.awesome.systray() is called. Notice that capi.awesome.systray() is called without arguments
from systray.fit(), so systray_register() is not reached in luaA_systray(). The consequence of this is
that the systray won't get any client and thus won't be updated. This implies systray.draw() is never called.

One fix is to call systray_register() before the if(lua_gettop(L) != 0) conditional:

int
luaA_systray(lua_State *L)
{
    // do this first
    if(globalconf.systray.parent == NULL)
        systray_register();

This way as soon as systray.fit() is called clients are able to register with the systray and update events
get generated.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1293#comment4120

(Continue reading)

awesome | 18 Aug 05:15 2014

[awesome bugs] #1293 - Systray won't show with margin layout

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1293 - Systray won't show with margin layout
User who did this - Carlos (memeplex)

----------
I've found out where the problem is. systray.fit is returning 0 both when the margin layout is used and also
when not. So the problem couldn't be there. But systray.draw is called only when the margin layout is not
used. So there must be something in margin.draw that makes reaching systray.draw impossible. Indeed:

    if not self.widget or width <= x + w or height <= y + h then
        return
    end

This will fail because of the condition width <= x + w. As num_entries = 0, it must be width == x + w.

One way out is to ask for width (and height) to be strictly less than x+w (and y+h), although this will render
the borders of a zero width (or height) component. Another way out is to avoid having widgets that aren't
able to calculate their geometry before draw is called for the first time. I'm not sure, I'm no expert.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1293#comment4119

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

(Continue reading)


Gmane