THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

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

User who did this - Emmanuel Lepage Vallee (Elv13) 

Attached to Project - awesome
Summary - Tag "index" is not handled properly
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 - In the current awful.widget.taglist implementation, everything is 
reloaded when something changes. This in itself solve a lot of issue, but has 
some limitations. My Blind library relied on a ton or very dirty hacks to keep 
track of states and display the correct content. These days, I use a new 
Radical based implementation. It is much easier to extend and even a little 
faster because of the lower rate of reloads.

The problem is that capi.tag/awful.tag implementation of tag indexes is 
currently broken. See

tag.connect_signal("property::index",function(t,i)
  print("A tag index changed",t,awful.tag.getidx(t),t.name)
end)
print("deleting a tag")
awful.tag.delete(awful.tag.gettags(1)[1])

When adding/removing/moving tags, the signal is not called. This, in turn, 
cause my implementation to just fail to reflect the current order, so both tags 
"number" (aka: "(1) Term") is wrong and the keyboard keys wont select the tag 
you expect them to select.

I could solve that by keeping track of the indexes myself, but that would suck. 
The current way indexes are managed is just wrong. It is both slow and buggy. 
What do you think would be the best way to handle this?

The "cheap way" to fix this is add 


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

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 [email protected].

Reply via email to