summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUli Schlachter <psychon@znc.in>2015-04-05 14:02:01 +0200
committerUli Schlachter <psychon@znc.in>2015-04-05 14:02:01 +0200
commit2d0d25aae08f5ca5de691c016e995c21a977c664 (patch)
tree9b3b014cd4080eaac779f549bcba138d3204f4eb
parent964a2b53500ed9af63528375d48d6805c5c11998 (diff)
Update KNOWN_ISSUES (and turn it more into a TODO)
Signed-off-by: Uli Schlachter <psychon@znc.in>
-rw-r--r--KNOWN_ISSUES12
1 files changed, 4 insertions, 8 deletions
diff --git a/KNOWN_ISSUES b/KNOWN_ISSUES
index 53482eb..4049a90 100644
--- a/KNOWN_ISSUES
+++ b/KNOWN_ISSUES
@@ -1,8 +1,4 @@
-- XGE and XKB events are not handled correctly (Should another API for this be
- added? Does it perhaps really make sense to have an API which gets an
- xcb_generiv_event_t*)?
-- I'm not sure about xcb_errors_get_name_for_minor_code() being able to return
- NULL
-- Should the extension's name be included in strings for that ext? More
- generally, think about how this library can be used and if such usage would
- result in "good" messages.
+- API docs with examples on how to use this
+- Does the name still seem correct? Figuring out event names turned out to be
+ more complicated than errors. Oh and we also handle requests...
+- Should releases come with pre-generated source?