THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below.
User who did this - Daniel Hahler (blueyed) Attached to Project - awesome Summary - Postpone/block layout (re)arrangement during applying of awful.rules / manage signal Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Medium Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - Could the layout (re-)arrangement get postponed during the execution of the "manage" hook? I have just debugged an issue with my config, where starting a new client that was set to floating in a function connected to the manage signal (after awful.rules.apply) caused screen/layout flickering. Setup: 1. tile layout 2. one master client 3. start a new client, which gets set to floating through a custom "manage" signal handler There were quite a lot of calls to arrange/do_tile and the number of master and other windows changed inbetween them. I could fix the particular issue at hand by removing disconnecting the default signal and attaching it again after my function. btw: I've noticed that client.floating.set alone can trigger (at least) two re-arrangements, via client.property.set and c:geometry. v3.5.2-203-g03aaf9a More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1306 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. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
