matt.baker

Unfortunately, it doesn't produce as good of a result when compared to PS and requires lots of messing around to get it close when dealing with complex cut-outs.

This is the only thing for me that keeps me using my old version of Photoshop. It's so simple to use the magic wand tool on a an image with clear edges to create a good cut-out in PS, but in AD it creates a horrible jaggy edge. I see that you already support anti-alias for the freehand selection, so I'm surprised it hasn't also been added to the magic wand tool. Or is it because it's the freehand selection creates a vector selection (while drawing) and therefore easier to anti-alias the edges vs. antialiasing a pixelated selection? Actual: Expected:

= and + share the same key (ignoring numeric keypad which may not be present on all devices) on common keyboard layouts, with = being the default and + only working if shift is also pressed. Ctrl + = seems logical to me because it functions without the shift modifier. Ctrl + + could imply that the shift must also be pressed.

Forgot about this, sorry. I tried it on my work PC and could not reproduce the issue, but it's still occuring on my home PC. It doesn't occur with other applications as far as I'm aware. I'll try uninstalling / adjusting settings and see if I can resolve it.

First use of AP in a while and it immediately breaks... Create a new document. Drag a Photo or Designer document into a newly created document from Windows Explorer/Desktop. AP hangs (still responding to Windows message system / no 'not responding' message). Window is not draggable. [Redacted] Example document below House template.afdesign xNV7wseEGS.mp4

Thanks. I'll do so more testing tomorrow on my work PC to see if it's the same.

If I use the window resize handles to increase the width or height the window, it doesn't update with the new size until I release the mouse. It works as expected when decreasing the width or height. RSQRu3Vvso.mp4

Thanks Chris So the cursor for the shape icon always looks like video 1, regardless of the the scaling when you tested it? Video 1 - Good Video 1 - Good.mp4 Video 2 - Bad.mp4 Video 2 - Bad Video 2 - Bad.mp4 Yes, this still happens on a standard HD monitor if the scaling is not a multiple of 100. 200% seems to be better and shows more white around the edges. Still not as crisp as the 100%, although that may be by design. From the original thread: Both setups are dual/triple monitor, but I've just tried disabling the extra displays and it still happens on either of the displays individually. On a side note, is there any way to limit the embedded video width in these posts?

Displays are running at their native resolution in both instances. How strange. No wonder it's never been picked up. Display drivers are different on both machines as well: one is Intel and one is AMD.

It's a 32" screen, but I've just verified that it also occurs on my work PC with a HD monitor when setting the display scaling to 125, 150 etc.% from the in-built Windows Display Settings dialogue. Just to clarify, as the gif and video may be reducing fidelity, it only seems to be ones that use the cross-hairs such as the shape tools and text. Compatibility options are off:

There's a cross-hair cursor below if you look really carefully. How the cursors appear on my PC: 4K display, 150% scaling, Windows Version 10.0.18356 Build 18356 (also happens on mainstream release). ZB9oUt2mPY.mp4 Please can you fix these. It's been like this for a long time now. Previous thread:

If you draw a line and then adjust the length numerically using the transform dialogue with lock aspect ratio still active (even though the width is 0 and greyed out), the output is not as expected from a user's perspective (programmatically it might be correct).

Gloucester / Cheltenham

Ah, I see. I've tried it at my workplace which uses BT + Virgin (one line for redundancy), and at home using TalkTalk, but both had the same slow speeds. I've tried it again at work and it's gone all the way up to ~95 kB/s, but still very slow.

Cant seem to reproduce this now, so I can only assume that it must have gone into an odd state and cleared once app re-opened.