Before it would show all unbound keys as duplicates (red)
Won't work for 1.52
Thats a pretty sophisticated way to write <= 0 in this case. :)
I can not reproduce the problem that this PR supposedly solves. An action for which the assigned key is unbound (deleted) is shown as...well, nothing in the "Assigned keys" column in the configuration dialog.
The keys on the bottom are all "unbound", but show up as duplicates in red. I think explicitly showing that they are unbound should be much clearer to users.
Edit, or we can just not show any text, but I think it's good to get rid of the red duplicate text.
@Killswitch00 If there is only one key unbound in the category it will show up empty (this is fine), but due to empty actually being it's own "key" it will show up as a duplicate bind when having more empty binds.
Thanks for the explanation and screenshot.
As mentioned elsewhere, how about displaying unbound keys as they are displayed in the normal game key assingment dialog, ie with the assigned key field empty? (As PabstMirror said, it would save us the trouble of translating the [UNBOUND] string)
Show when a keybind is unbound
Fix private and mark dikCode -1 or 0 as unbound
Just show blank space for unbound keys