Demo QOL improvements

[rswinkle]

I have two minor changes to suggest and I'm happy to do them myself.

1. A meaningful window title, ie "SDL Renderer", "SDL OpenGL3", "GLFW Vulkan" or similar to indicate which backend it's using. This would make it much easier to track which window is which when you're running multiple for visual comparison.
2. A standardized method to exit via the keyboard. I'd recommend ESC except that seems to be used for NK_KEY_TEXT_RESET_MODE so instead I suggest something like CTRL+Q.

I was about to dive into finally giving that "meta-backend" idea of mine a go when I realized I didn't want to deal with testing it without these (especially 1) in first.

Thoughts?

@RobLoach @sleeptightAnsiC

[RobLoach]

1. nuklear_demo_sdl3 for the window title?
2. What's against ESC? I think it's fine, but could be missing something about how text repeat works

[rswinkle]

1. nuklear_demo_sdl3 for the window title?

I'm fine with whatever as long as it's clear which one it is. We could just have them match the folder names so sdl3_renderer, glfw_vulkan and so on. nuklear_demo_sdl3_renderer is getting a bit long but either works.

2. What's against ESC? I think it's fine, but could be missing something about how text repeat works

I definitely prefer ESC. It's quick and easy and I honestly don't think it's getting used in the demos. I think I had to use when I was fixing an insert/overwrite issue or something similar a while back but other than that, never. These are just demos after all and it's the backend that matters more.

If you're ok with ESC I'l go for it. Final say on the title format?

[RobLoach]

Makes sense to me. Definitely more descriptive than the current one.

[sleeptightAnsiC]

This textfield, for example, respects Insert and Esc

Nuklear/demo/common/overview.c

Lines 633 to 634 in 9afb3dd

	nk_label(ctx, "Field 2:", NK_TEXT_LEFT);
	nk_edit_string(ctx, NK_EDIT_SELECTABLE|NK_EDIT_CLIPBOARD, field_w_overwrite_buf, &field_ow_len, 64, nk_filter_default);

and NK_KEY_TEXT_RESET_MODE is something that I had to test in the past for edge cases (e.g. #857 (comment) )

[rswinkle]

This textfield, for example, respects Insert and Esc

Nuklear/demo/common/overview.c

Lines 633 to 634 in 9afb3dd

nk_label(ctx, "Field 2:", NK_TEXT_LEFT);
nk_edit_string(ctx, NK_EDIT_SELECTABLE|NK_EDIT_CLIPBOARD, field_w_overwrite_buf, &field_ow_len, 64, nk_filter_default);
and NK_KEY_TEXT_RESET_MODE is something that I had to test in the past for edge cases (e.g. #857 (comment) )

Yes, it does, because I added it explicitly to test/fix those features when I added that capability to the backends only last year. That means we went for over a decade without any support for insert/overwrite/reset in the demos and thus ESC was never used. I almost removed it once I was done with my PR too.*

The point is, using ESC to exit is not really a big deal since no one not explicitly trying to test such a rarely used, barely known feature only applicable in a single text field would even notice. Anyone who needs to test the feature can simply edit the line in the demo when they do.

If both of you feel strongly about it I will stick with my original alternative of CTRL+Q but it is less ergonomic/standard and more code/uglier (more of an issue since we handle events inline in the main loop):

        while (SDL_PollEvent(&evt)) {
            if (evt.type == SDL_QUIT) goto cleanup;
            if (evt.type == SDL_KEYDOWN && evt.key.keysym.sym == SDLK_Q && SDL_GetModState() & KMOD_CTRL) goto cleanup;
            nk_sdl_handle_event(&evt);
        }
vs
        while (SDL_PollEvent(&evt)) {
            if (evt.type == SDL_QUIT) goto cleanup;
            if (evt.type == SDL_KEYDOWN && evt.key.keysym.sym == SDLK_ESCAPE) goto cleanup;
            nk_sdl_handle_event(&evt);
        }

*Technically a couple supported RESET and used escape but not insert/overwrite and none of the major ones (SDL and GLFW supported any of them. And since nothing in the overview actually used them it was moot even for if they had supported them.

[RobLoach]

If escape conflicts with other uses, I think CTRL/COMMAND Q would work. It is a standard across other applications, so 🤷

[TomJGooding]

https://www.youtube.com/watch?v=TpQlyUjp3vM