Skip to content

Fix issue selecting fully transparent pixels in fill and contiguous selection tools

Two fully transparent pixels can have different color components. This can happen when erasing with a brush (only the alpha component seems to be set). Those pixels should nevertheless be considered equal (transparent pixels).

In the difference policies used by the flood fill algorithm there is a special case for when the threshold is 1. In that case the pixels are just compared with memcmp and those fully transparent pixels with different color components are then considered not equal. A check for the fully transparent colors must be put in place similar to how differenceA does it, otherwise a contiguous transparent region may not be totally selected if the color components vary.

A video showcasing the issue (first half: old; second half: new): https://youtu.be/LMbiTx4DZrE

Formalities Checklist

  • I confirmed this builds.
  • I confirmed Krita ran and the relevant functions work.
  • I tested the relevant unit tests and can confirm they are not broken. (If not possible, don't hesitate to ask for help!)
  • I made sure my commits build individually and have good descriptions as per KDE guidelines.
  • I made sure my code conforms to the standards set in the HACKING file.
  • I can confirm the code is licensed and attributed appropriately, and that unattributed code is mine, as per KDE Licensing Policy.

Reminder: the reviewer is responsible for merging the patch, this is to ensure at the least two people can build the patch. In case a patch breaks the build, both the author and the reviewer should be contacted to fix the build. If this is not possible, the commits shall be reverted, and a notification with the reasoning and any relevant logs shall be sent to the mailing list, kimageshop@kde.org.

Edited by Deif Lou

Merge request reports