Vasilij Schneidermann

Can you provide actual hard numbers? It's otherwise hard to tell whether there's been an improvement by a change. I have one in mind that might help with this issue...

I mean something like running `font-lock-profiler-buffer` on the problematic buffer. edit: Results: Modified: ``` 0 0 0% ("^ " (0 form-feed--font-lock-face t)) 10 0 0% ("[{}]" (0 font-lock-builtin-face)) 12 0...

Note that you can already choose the backend by using the `BEMENU_BACKEND` environment variable.

Something like `(1+ )`, with `` highlighted distinctly. That way one would immediately know what the problematic part is.

Using `KW_SetClipChildrenWidgets` for the first approach appears to have no effect. I'll rewrite my current example in C and submit it here soonish. The only reason I suggested the second...

Program: ``` c #include "KW_gui.h" #include "KW_frame.h" #include "KW_label.h" #include "KW_button.h" #include "KW_renderdriver_sdl2.h" KW_Widget * messagebox; void ok_clicked(KW_Widget * widget, int button) { KW_DestroyWidget(messagebox, KW_TRUE); } int main(int argc, char...

Cool, that works! Somehow it's still feeling off for me, probably because this message box looks very much unlike anything else I've seen and is transparent. Code: ``` c #include...

That helps, but if I were to use that tileset with the styleswitcher example, frames would look pretty weird as a frame is used there like a pane widget which...

That does indeed look like a solution, but won't do as soon as there's some convenience function for opening a message box.

Hm, not sure. It doesn't sound much different from using two frames, one for the normal window, the other for a message box, then blocking input events for the former...