-
Updated
Oct 21, 2020 - GDScript
pixel-editor
Here are 36 public repositories matching this topic...
-
Updated
Sep 10, 2018 - CoffeeScript
-
Updated
Oct 20, 2020 - Java
-
Updated
Jul 25, 2018 - Pascal
-
Updated
Jan 27, 2020 - Swift
-
Updated
Mar 11, 2020 - C++
-
Updated
Oct 22, 2019 - Vue
-
Updated
Sep 22, 2020 - C++
-
Updated
Mar 6, 2015 - Haxe
-
Updated
Oct 17, 2017 - JavaScript
-
Updated
Sep 20, 2019 - Python
Make time remaining label appear/disappear whenever a render starts and stops.
i.e. visible when underway, invisible when not.
Simple ui change but makes it look nicer
-
Updated
Aug 16, 2019 - Python
-
Updated
Jan 26, 2020 - JavaScript
-
Updated
Jan 6, 2018 - JavaScript
-
Updated
Nov 7, 2016 - JavaScript
-
Updated
Sep 9, 2020 - JavaScript
-
Updated
May 17, 2019 - Swift
-
Updated
Dec 18, 2018 - JavaScript
-
Updated
Aug 4, 2019 - C#
-
Updated
Aug 2, 2020 - Java
-
Updated
Jul 9, 2017 - Swift
-
Updated
Mar 31, 2017 - C#
-
Updated
Sep 11, 2020 - JavaScript
-
Updated
Sep 9, 2018 - Python
Improve this page
Add a description, image, and links to the pixel-editor topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the pixel-editor topic, visit your repo's landing page and select "manage topics."
Currently, when an action is performed (example: drawing a pixel), the action is re-performed when it's initially done and when it's re-done (after being undone).
If someone was to create a big canvas, fill it, then undo it, re-do it, the program might lag, as it's being re-performed every time.
To aid this, an action should be "cache-able", meaning that whatever the action does is saved to