Jump to content
You must now use your email address to sign in [click for more info] ×

Transparency tool damages pixel layer


Recommended Posts

Steps to reproduce 

  1. create new document
  2. create pixel layer (e.g. rectangular shape, fill blue, rasterize
  3. Activate transparency tool
  4. change type from „none“ to linear
  5. the pixel layer gets destroyed and replaced by gradient from white to transparency. No handles/nodes to adjust effect
  6. On vector layers, you could change type to none any time later to restore original status. On pixel layers, damage is final and unrecoverable (except undo)

I’m aware that help says tool is for vector layers. Never the less, it should not cause harm to document layers if applied by mistake (e.g. wrong layer active in layer panel).

PS: My request is to either ignore pixel layers (cause no damage), or make it usable (created nested vector shape with gradient). In the current state it is a undocumented trap for unexperienced users.

transparency tool destroys pixel layer.afdesign

Edited by NotMyFault

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

Gradients have always completely replaced Pixel layers, as Pixel layers have only their Pixels, and not a separate Fill that can overlay them. And Gradients on Pixel layers are never adjustable, either. 

Not a bug, as far as I know.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

8 minutes ago, walt.farrell said:

Gradients have always completely replaced Pixel layers, as Pixel layers have only their Pixels, and not a separate Fill that can overlay them. And Gradients on Pixel layers are never adjustable, either. 

Not a bug, as far as I know.

Half logical and typical example of consequential implementation, but clearly no show case for user friendly UI.


It should work either completely (showing nodes to adjust gradient), or not at all (do not activate on pixel layers).

This mix of replacing pixel content, but no option to adjust handles makes no sense to users.

i would be ok if Affinity removes the transparency tool for pixel layers totally, to avoid this unexpected damage.

On the other side: it could simply create a vector shape with gradient, and nest it to masking position (similar as vector crop does), and leave the pixel layer intact.

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

Sounds like a good Feature Request.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

  • 1 year later...

issue was fixed in 1.10 and V2

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.