Bug 371555 - Custom pixel brush paints a pixel after erasing using a pixel eraser
Summary: Custom pixel brush paints a pixel after erasing using a pixel eraser
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Brush engines (show other bugs)
Version: 3.0.1.1
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-10-24 04:18 UTC by andrey.aik
Modified: 2018-10-28 03:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andrey.aik 2016-10-24 04:18:59 UTC
I've customised the pixel brush so that it is 1px in brush size, and this was the only setting that I've modified for the custom pixel brush. One of the custom brushes is set to the Normal setting and the other brush setting is set to Erase. When I'm using the Erase pixel brush to erase pixels using the stylus eraser after using the Normal pixel brush on the stylus pen tip, it draws a pixel after lifting the stylus eraser from the screen. This is not meant to happen because there shouldn't be a pixel drawn after lifting the eraser stylus from the screen. I'm using the Microsoft Surface Book with the N-trig stylus.

Reproducible: Always

Steps to Reproduce:
1. Create a custom pixel brush (derived from PixelArt_Square) with the pixel size set to 1 and type set to Normal
2. Create a custom pixel brush (derived from PixelArt_Square) with the pixel size set to 1 and type set to Erase
3. Draw on the screen using the stylus tip
4. Erase drawn pixels (or pixels that are not drawn) on the screen using the stylus eraser
5. A pixel should appear on the screen after lifting the stylus eraser

Actual Results:  
A pixel is drawn on the screen after lifting the stylus eraser from the screen.

Expected Results:  
Not draw a pixel / do nothing.

Computer configuration: Microsoft Surface Book (with i5 processor and nVidia graphics gpu configuration)

Memory: 8gb of RAM
Processor: 6th Generation Intel® Core™ i5
Storage: 256gb solid state drive
Graphics: NVIDIA GeForce GPU with 1GB GDDR5 memory
Comment 1 Halla Rempt 2016-10-24 07:58:01 UTC
Can you please attach your custom brush (the .kpp file) to the bug report?
Comment 2 Halla Rempt 2017-02-27 18:54:06 UTC
Without the custom brush, we cannot investigate this bug.
Comment 3 Andrew Crouthamel 2018-09-28 02:32:42 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-28 03:31:30 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!