Problems using Imgui's "use skia space"

[schlonzo]

hi all,

got some interesting imgui behaviour when using the “use skia space” pin on the imgui region; (when I activate the “skia pace pin” my skia space topleft corner starts in the middle of the screen and the interface gets giant and somehow pixelated; I had to skia transform the whole interface to match the original layout.

I layouted an imgui menu on a machine with 2160p display and 175% windows scaling. On this machine the interface looks ok. already a little more low res than when not using the pin, but OK.

when opening the patch on a machine with 1080p and 100% scaling it looks like this:

and when opening on a machine with 1440p it looks like this:

any ideas what is happening here?

[bjoern]

Idk if it is still the same behaviour/bug but in earlier versions of VL.Imgui it didn’t correctly deal with display scaling and I didn’t really get an answer back when I posted it.
See:

TexConvGui NG

Added a compiled exe on the TexconvGui contribution page . @ImGuiTeam VL.ImGui still has problems with Display scaling. Added a workaround, multiplying the widget sizes by DipFactor in the patch, still the result doesn’t look quite correct for scalings other than 100%. Another “bug” I encountered: Setting a padding for the window also increases the padding of tooltips which shouldn’t happen imho.

TexConvGui NG

I think this is outdated. There is a node called Disable(d?) with a Widget input now. All widgets that have sizes set explicitly (Witdh / Height) don’t scale correctly if the Display Scaling is set to something different than 100%. So an Input (String) with Width set to 200 for example will only be 100 wide when the display is set to 200%. I have a branch on github where I “manually” multiply all sizes with DipFactor as a workaround, which is better, but still doesn’t look quite correct. I…

Another thing that might be related is how vvvv deals with window sizes / display scaling in general.
If one saves a window with a size of 1000 x 1000 px at 100% scaling and then opens the patch at 125% for example the window will open with a size of 1250 x 1250 px. Imo this isn’t correct and the size should rather be “absolute”.

[ziopix]

Hi all,
Any news or work around regarding this topic?

I noticed the problem also in the help patch “Example Interoperate with Skia.vl” where seems the actual space usable is a 1/4 of the full space, maybe I’m doing something wrong. If you try to move one point of the triangle you will notice that ImGui primitive triangle will be not rendered, same happens if you try to move the button with a “SetCursorPosition” node.