Construct 2 on high DPI monitors?

I'm curious, as there hasn't been a lot of discussion regarding this issue on the forums. There's official support for running Construct-built games with DPI awareness, but what about running the editor itself on high DPI devices?

When running the editor under screen resolutions comparable or higher than retina displays, the editor breaks, tears, and hiccups. This can be fixed by changing the OS window scaling below 150%, but it results in everything being rendered unreadable. The compatibility issues are ugliest when in the event sheet editor, where dialogue boxes overlap radio or form boxes and commands on the edit action/condition windows vanish when they are moused over.

Here's an example:

<img src="http://i.imgur.com/sc3EiTh.png" border="0" />

Another example:

i.imgur.com/G6fnTb3.jpg

In the above URL, you can see that set scale, size, width, x, and y have all vanished from the size and position action set. This is another issue that occurs when using Construct 2 on high resolutions.

So my question for now is, does anybody else out there develop with Construct 2 on high DPI displays? I realize it's a real shot in the dark to try and ask for any feedback or improvements made for emerging technologies, but if Construct 2 is really billing itself as a future standard, then there must be something that can be done to alleviate high resolution woes.

I'm using a 2560x1440 27" monitor, so I don't think I really fall into the High DPI category, but I've had no issues running at this res at all.

I know it's not exactly a helpful answer, but thought I'd just throw it out there <img src="smileys/smiley1.gif" border="0" align="middle" />

At least one of those issues is a bug we fixed in r152: the dialog button positions got messed up if you changed DPI setting. Workaround: hit 'Reset dialogs' in Preferences. In r152+, it detects DPI changes and resets dialogs automatically.

Ah, okay. I'm currently running r152 at a resolution of 3200x1800. I think 2560 counts as high DPI as well, but I'd assume this is a large enough jump for the pixel density to be different.

I did try resetting all dialogs as recommended, but I still come back to this very problem. I might be able to get a hold of another machine with a comparable resolution and fresh install to see if I can reproduce these display issues.

EDIT: I've just made a fresh install on a new machine with the same kind of display and resolution. Construct is still exhibiting the same issues as before.

I think the issue is mostly isolated to improper dialogue box scaling in C2 when windows scaling is enabled to 200% at high pixel densities (around 275 dpi). I'm going out on a limb with this one, so I hope somebody else out there can add some additional testimony to this..

I'm taking a bit pot shot guess here so take my opinion with a grain of salt. Ie. I'm really guessing out my butt here.

The world of high DPI for desktop use is still a little newer and not as main stream. I know they've come into play in the couple of years but it's still not a main stream thing. I think any IDEs that include form editors and such are gonna have to have a break in period to resolve this kind of stuff. I also don't know how Construct develops their program (if they use a form editor to make the windows or do it by hand) so that might make a difference as well.

I'm a little inclined to say your opinion leans toward fact!

Seems the complications of high pixel density technology means anybody using these kinds of displays will have to create some kind of alternate resolution profile when working in Construct for the time being.

I really appreciate the timely response from Ashley, it's inspiring to know that attention has been paid to so many emerging trends, even if it is still quite early to provide a decisive fix on the issue.