Copy link to clipboard
- If you're using a gradient layer with a mask, the gradient doesn't correctly fit to its bounds
- If you're using artboards and have content outside the bounds of the artboard, the gradient will size to that, rather than to the artboard
There's also no red-line snapping, so its difficult to align the gradient precisely yourself.
Hi @fleacircus thank you for the post. Would it be possible for you to share a video ro screenshot of what you are seeing for the team?
It may help if we could see your Photoshop System Info. Launch Photoshop, and select Help >System Info...and copy/paste the text in a reply.
1. Linear (method) gradients aren't linear: https://youtu.be/p1whSUs9G6M
'Classic' method gradients are more linear than 'Linear' method gradients, to the point where I wonder if you've got the labels wrong in the UI.
2. Gradients fit to wrong document bounds: https://youtu.be/3Ux8bOWNLgQ
Goes on the pile of tedious artboard bugs, along with 'Filter -> Other -> Offset doesn't wrap on Artboards' and 'Cropping an artboard doesn't remove content outside the bounds'.
3. Gradient doesn't correctly align with layer: https://youtu.be/Q7FH0ToIDuU
The behaviour of 'Align with layer' and 'Reset alignment' buttons is surreal, giving different results depending on if they're clicked in the Popup window or the Properties window (which is missing the 'align with layer' checkbox).
As far as I can tell, the issue stems from the Properties window 'Reset Alignment' changing the 'Scale' percentage, but the Popup window 'Reset Alignment' not.So two different buttons, with the same name, surrounded by near identical controls, each with slightly different behaviour.
I guess this message is more for the managers who will never read it but nevertheless: I understand a codebase from the 90s is likely extremely difficult to work with, but with the horrific amount that Photoshop now costs, I expect far better. I'm using Photoshop and a custom UXP plugin as part of a game engine and *easily* the majority of this development time has been spent fighting obscure bugs, poor documentation, bad UX and half-supported features.
I've just lost another hour of development time recording videos of bugs for a product that must *easily* bring in over $70mil *per month* to the company. Sure, it's a beta and bugs are expected, but I could report 10 more bugs from the current release too.
Also, I'm *on* the beta because after years of UXP being developed, it's the first version where I can actually get the contents of a type layer (but still has broken, ugly web components and CSS because Chromium was inexplicibly gutted and now doesn't support your own design system). I'm writing the UXP plugin in the first place to replace the official 'Generate Assets' plugin that doesn't support 16-bit assets and appears abandoned.
The *instant* another product ticks enough boxes, we will be moving away from Photoshop and Adobe, who keep charging more money for worse products.