New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE] Bitmap layer doesn't refresh after deleting the layer #920

Kaikogf opened this Issue Mar 12, 2018 · 2 comments


None yet
3 participants

Kaikogf commented Mar 12, 2018

--Actual Results--

Two issues when using bitmap layers

--Steps to reproduce--

  1. Open Pencil2D

  2. Use the default bitmap layer already selected and draw some lines with any tool you like, use a red color (just for visualization)

  3. Add a new bitmap layer

  4. Add again another bitmap layer (this step is not necessary though

  5. Now delete one layer (which means that you are going to delete the first layer with the red lines lines since no other layer was selected). Use no shortcut keys

  6. Result: The red lines are still there on the canvas

  7. Select another color (blue) and draw some lines on the canvas. When you release the pen the red lines will be covered by a white square surrounding the blue lines and eventually will disappeared in just a few seconds leaving the canvas with blue lines only (not always happens this way)

--System Information--

  • Pencil2D Version:
    Last build 11March2018

  • Operating System:
    Windows 8.1 x 64bits

  • RAM Size:

  • Graphics Tablet:


This comment has been minimized.

Kaikogf commented Mar 12, 2018


In step "6", if you select another layer all the lines on the canvas will disappear. If selecting a Tool instead of a layer, lines will not disappear

@chchwy chchwy added the bug label Mar 12, 2018

@chchwy chchwy self-assigned this Apr 17, 2018

@chchwy chchwy changed the title from [ISSUE] related to Bitmap layer to [ISSUE] Bitmap layer doesn't refresh after deleting the layer Jun 5, 2018


This comment has been minimized.


Jose-Moreno commented Jun 16, 2018

Can confirm this issue is still happening in the latest nightly build for June 13th.

@chchwy chchwy closed this in 149f6c0 Jun 17, 2018

@chchwy chchwy removed their assignment Aug 6, 2018

@chchwy chchwy added this to the 0.6.2 milestone Aug 6, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment