Open aphirst opened 4 years ago
do you mean those?
I may mean those, yes! I am currently trying to work out, either from the code or from people in the ibus community, which properties are used for these dialogs, as there's another one (the emoji selector) that isn't helped by setting just the one parameter I mentioned in my OP. Sorry about the delay, but when problems lie at the intersection between unrelated projects, I figured it was best to gather that info before jumping any guns.
TBH i never used that feature of oomox theme myself, it was added by @cwendling here: https://github.com/themix-project/oomox/pull/69 mb he could help to debug this
I'm not quite sure, but maybe that's a specific use case of IBus. I see that in my MR @actionless linked, I set the property on something more specific than *
, so that might be the problem. I don't remember if there was a reason to do that apart that GTK only used it there (in views and entries), but I see 2 solutions: set it more globally, or make sure the IBus panel has the proper view
class or so.
I've been very satisfied with oomox on my new setup, using my preferred and familiar numix brave theme.
I am however also a user of ibus for Japanese input, and it seems that the defaults for the oomox themes do not set all the necessary values. https://github.com/ibus/ibus/issues/1871#issuecomment-271918685
The accessibility overlay defaults to a black background, and with black text it obviously means you can't read the kanji selections.
If I manually set
gtk-secondary-caret-color
like in the linked thread to be the same color as, say, Selected Background (729fcf for shiki brave, for example), I get the desired behaviour (legible text).Has this value been deliberately omitted in the generator?