Rokas Kupstys

...brainstorming continued. So pixel grind misalignment... Black grid is physical pixels. Red grid is our virtual 96 DPI grid (where DPI=1.5f). Problem is rather obvious now.  Position `(1.f, 1.f)`...

Shaking fix is in place. I also made screenshots of docking branch vs hdpi branch to see if my changes do not break stuff in default setting. I am fairly...

I think we are at the point where we can start taking a close look at current implementation and what we need to do further. Here are some things to...

I implemented support for `ImGuiConfigFlags_DpiEnableScaleViewports`, but i am unsure of it's usefulness. Do we want to keep this flag or should it be removed altogether and enabling viewports should imply...

Hey awesome someone else is looking into this and exploring alternative solutions! I overlooked font oversampling. Need to investigate it again. But would it work in a situation where we...

I am exploding different HDPI support approach. Please see end of the first post for a detailed description and link to the branch if you want to test it.

If anyone is interested - there is another experimental branch implementing a different approach we are exploring. This approach implements multiple font atlases for each unique DPI value and automatic...

You never explained why you want to do things you want to do. Chances are there is a better solution, but we can not point you the right way if...

Im sorry for a late reply. @Fredrum your issue is using selected option as a button string in `if(ImGui::Button(select.c_str(), button_sz))`. String passed to `Button()` is used to calculate button widget...

I have incorrectly stated need to use `##` separator. I constantly confuse them.. Library supports `##` and `###` separators that both serve different purposes. - `##` is to be used...