[awesome bugs] #1296 - Updated signal causes total relayout (Attachment added)

2015-01-11 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- It's time for a new version! This one adds an API change to make Elv13 (hopefully) happy: -

[awesome bugs] #1296 - Updated signal causes total relayout (Attachment added)

2015-01-11 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- Sorry, but I think that the padding should be returned from :layout() instead of :fit(). New version

[awesome bugs] #1296 - Updated signal causes total relayout (Attachment added)

2014-12-06 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- TL;DR: I'd be interested in suggestions for the API. Once again, here is a new version (mostly

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-14 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- The area outside of the dirty_area in my code is not redrawn at all. So if a widget unsets the clip and

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-14 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Vlad Leberstein (owl) -- Psychon, I understand your approach and its limitations. Thats why I believe we should decide now if

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-14 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- Ok, glad that I seem to make sense and that you understand me. However, I don't feel like I understand

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-14 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Emmanuel Lepage Vallee (Elv13) -- The minus-pixel/over pixel would work, however if region A is painted over by region B, then if

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-13 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Vlad Leberstein (owl) -- Psychon, I finally got some time to try your approach and it seems very reasonable to me. But could you

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-13 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Emmanuel Lepage Vallee (Elv13) -- We also have to take into account scrolling layout:

[awesome bugs] #1296 - Updated signal causes total relayout (Attachment added)

2014-10-05 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- Another new version. This now introduces a layout cache similar to the fit cache. This removes the

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-05 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- Sorry for spamming. I tested a 45 degree rotation and quite some code broke. Here is the code for the

[awesome bugs] #1296 - Updated signal causes total relayout (Attachment added)

2014-10-05 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- Seems like I can't get this out of my head... All of a widget's callbacks are now optional. Missing

[awesome bugs] #1296 - Updated signal causes total relayout (Attachment added)

2014-10-05 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- Yet another new version of this proof of concept. Now, after re-layouting things, only the part of the

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-04 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- Is having multiple parents worth it: Even the default config makes use of this. It's a great feature

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-04 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- Uhm, a quick question: How much influence would this have for real-world widgets? Whenever a widget

[awesome bugs] #1296 - Updated signal causes total relayout (Attachment added)

2014-10-04 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- Attached is a quick prototype implementation of this. It only depends on gears.object and lgi. A

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-04 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Uli Schlachter (psychon) -- Oh and the systray needs some special magic as well since awesome can only place it, not redraw it.

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-04 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Vlad Leberstein (owl) -- Thanks for all the replies! It's nice to see the problem gets more attention! As for the reference

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-02 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Vlad Leberstein (owl) -- Thanks for your explanation and sorry for my late response! I've investigated a little bit further and now

[awesome bugs] #1296 - Updated signal causes total relayout

2014-10-02 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Emmanuel Lepage Vallee (Elv13) -- The bottleneck is the exponential overhead caused by LGI. This is much better with 0.8, but far

[awesome bugs] #1296 - Updated signal causes total relayout

2014-09-05 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Vlad Leberstein (owl) Attached to Project - awesome Summary - Updated signal causes total relayout Task Type - Evolution Request Category - wibox Status - Unconfirmed

[awesome bugs] #1296 - Updated signal causes total relayout

2014-09-05 Thread awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1296 - Updated signal causes total relayout User who did this - Emmanuel Lepage Vallee (Elv13) -- Yes, you are right. The widget::updated signal is propagated back up, then, when it reach the