Skip to content

Conversation

duarm
Copy link

@duarm duarm commented Oct 27, 2022

just creates an IM context to be used later, this shouldn't affect anything aside from requiring

#include <xcb-imdkit/imclient.h>

before including libgwater_xcb.h, is this desirable? or I missed something the way the headers are handled?
the context is only put to use when calling xcb_xim_open()

@duarm duarm mentioned this pull request Oct 27, 2022
4 tasks
@sardemff7
Copy link
Owner

First: Reading the code in its current state, I see no reason to include it in libgwater .
It doesn’t interact with the main loop and you only need an xcb_connection_t which is provided already.
If it needs to be created in a special way at a special moment that lies in libgwater, I think the _for_connection variant can be used, with an off-loaded xcb_connection_t

TL;DR: it doesn’t belong here, IMO, so I will close this MR

Now, thanks for the effort, and I still have a review comment: when you contribute to a project, please, follow the style that is already in place. Here, specifically, no “long lines wrapping” and the { on their own line. 🙂

@sardemff7 sardemff7 closed this Oct 27, 2022
@duarm
Copy link
Author

duarm commented Oct 27, 2022

ok, that method wrapped two times on my editor, thought it was harmless, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants