Free Trial

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Designer: 4k/UHD scaling

Hi there,

 

Just got a new 4k UHD monitor, and found that Alteryx Designer doesn't scale well in default settings in Windows.    Fonts are blurry but icons are the right size.

If instead you change compatabilty mode to allow the application to force scaling, then the fonts and icons end up all different sizes.

 

Could you change the fonts and icons to scale gracefully in Windows 10 to full 4k UHD HDR - especially on the large size monitors (30 inch plus)?

 

 

 

 

Shot 1: default mode - blurry text - badly scaled by Windows 10.    It's not easy to see here because the image is small - but all the text is blurry like a badly blown up BMP file.

scaling2.PNG

 

 

Shot 2: Override Windows 10 DPI scaling and set to "Application" mode

You can see in the picture below that text is now super-sharp but the the play button; save button are all tiny; the fonts are different sizes (look in the properties tab on the left) etc.

 

scaling.PNG

12 Comments
biytc2
5 - Atom

Try opening your settings, go to display, and change the scale to 100% (It was 200% before I changed it), this solved my problem.

TeePee
8 - Asteroid

It's been a couple of years since there was activity on this thread.  With working from home, I'd like to connect my laptop to a wall mounted TV instead of my ugly monitor on my tiny desk so I tested it with a high quality cable: results: Tableau and other software looked perfect, but Alteryx was blurry and pixelated.  As a pioneering piece of software that is ahead of the curve in many ways, this issue is long overdue a fix.  I see it's marked "Revisit" - please can you let us know when you plan to catch up with everyone else please?  As others have said, the other huge advantage is being able to see more of the workflow on a bigger screen. Thank you!  PS @SeanAdams did you manage to find a workaround by any chance or did you just give up?