Xeverous

>> Alternatively, namespaces could be used like `elements::controls::button` and `elements::layouts::htile` to separate internal and external APIs. > Interesting idea. Noted! I'll ponder on this. This might also solve some class...

What's the reason behind `-1` here? If I try `corner_radius = 0` will something break? https://github.com/cycfi/elements/blob/2aea4fcd03992c642fc45bbfd38268abab482160/lib/src/support/draw_utils.cpp#L81-L104

Got any objections for moving almost all color/geometry information into default theme? I would like to have much higher control over the look and experiment a bit (perhaps even make...

Do you have any recommendations where theme object should/should not be used? I see 3 possible ways: 1. refactor `draw()` to pass the theme object as a parameter 2. widgets...

I don't think such at-construction use of theme is good. You need to recreate the widget to apply theme changes - I would prefer it to be only 1 or...

I'm fine with reconstructing the root element, but not sure if it will actually apply the change. If the root element holds a shared pointer to some widget hierarchy, I...

> You rebuild the view content. For example, here's the point: I get the example but I mean such situation: ```cpp auto ptr = share(make_controls(view_)); view_.content(ptr, share(background)); // change theme......

> The font is a ref-counted handle. Great, that solves both lifetime and construction cost problems. I guess I should probably wait a bit with theme-related PRs as I will...

> @Xeverous, see if you can deal with the windows install. This is why I sometimes truly hate building specific C and C++ libraries. - linked pango website has no...

Wow, the image looks really good. > But that practice is going out of style, IMO. Synthesized styles will never be as good as true weighted fonts (e.g. bold) and...