Question: impact of GDK_SCALE on window positioning options

[step-]

Hi Victor, in the past have you considered the impact of $GDK_SCALE on yad window positioning options, such as --posx/y and --geometry? Recently I used a 4K (3840x2160) monitor. Since windows looked tiny I exported GDK_SCALE=2 to see them larger. TO my surprise, I saw yad --posx=100 --posy=100 placing the window at (200, 200) screen coordinate instead of (100,100). Do you think it is the right thing to do? Or should yad instead place the window at (100, 100) regardless of the GDK_SCALE value? This is a gray area in the man page. I don't have a preference. However, I want to make sure that your project and my fork adopt the same solution on this matter

Take a look at the screenshot below. The monitor is 3840x2160 (the picture is cropped). GDK_SCALE=2 is set in the environment. The pxruler shows "GDK dimensions" so it takes two screen pixels for every pxruler pixel. The smaller yellow ruler shows "screen dimensions", real pixels. Both windows are created with the same options, as you can see. The bottom one is twice as big as the top one -- that is correct behavior I think because doing otherwise would defeat the purpose of GDK_SCALE. But what about the positions of the two windows? Should yad place them as it does now as seen in the picture, or should it place both windows at (660, 340) screen coordinate, that is pin them to the same point?