- This was a huge pain in the neck, literally and figuratively.
- Saving: WORKING
- Opening: WORKING
- Overwriting: WORKING
- Wallpaper: (reply was never sent...)
- Add icons
- Add audio
- Add padding
- Add "default button" styling logic, where the default or focused button gets a bolder border.
- Tweak some dialogs, favoring localized and accurate renditions, rather than more modern, more specific button labels.
Enable resizable windows! And proper dialog window styles!
Tool window titlebar text is truncated with ellipses now instead of making the window ridiculously wide for some languages, e.g. Español which reads "Herramientas" for "Tools"
- Linux uses BrowserWindow icon option, but the filename was incorrect.
- Windows and Mac use packagerConfig, which differentiates on the file extension automatically, but the file names have to be the same otherwise.
I don't normally add to this todo list, I want it to only get smaller...
I have an external todo list with much more, that always grows,
but this is adding a lot of notes on a stated goal of the project.
- Underline works now!
- Re: "Keep an old OnCanvasTextBox while drawing a new one" - even tho this should be easy now that it's not using that object to represent in progress selections, I don't think I want to do this! I think the way it works now is better.
- Cancel the polygon if you end up within the auto-finalization distance on the first gesture
- Regarding "Don't start making the polygon until you click and drag more than the auto-finalization distance" - I don't see evidence for this. I think this was just a misconception based on the canceling.
- (PARTIALLY avoid a browser bug in chrome. When you zoom to a non-integer scale, there's this weird quantum antialiasing due to the canvas having a backing store which is higher density than the canvas's logical pixels (and redraw regions come into play as well). Switching to storing ImageData instead of canvases for undos/redos doesn't eliminate much of this problem, but it avoids having the undos/redos also store some high-DPI state and thereby SOMETIMES restore a state of whether antialiasing is happening or not. So it's a little less weird now, but it doesn't really solve that bugginess.)
- Protect against data loss when running low on memory. The browser (chrome at least) can clear canvases when low on memory. If the data is erased, and you undo, or do anything to the canvas, jspaint saves over the autosave. Ideally there should be multiple autosaves, but for now this is catastrophic in terms of data loss. Using ImageData instead of canvases, hopefully the browser is less willing to destroy this data, since it's more like a plain data structure in your program, and you would hope it wouldn't just delete arbitrary data in your program. A crash should be better than losing the canvas data (undos/redos) because in that case the autosave should still be in tact, altho this doesn't protect against the case where the main canvas is cleared by the browser, and then you do something to interact with the canvas other than undo/redo, and then either the page crashes or you refresh, and the autosave will still be gone.
- Behavior change or Regression: Now if the document is transparent, but the document mode is opaque, and you paste something larger than the canvas, it'll keep the transparency in the area of the original document, because it's using putImageData instead of drawImage.
- Regression: When you choose Opaque in the Image > Attributes... it no longer makes the document opaque because it's using putImageData instead of drawImage.
- Fix: Rewrite the Free-Form Select's temporary shape preview to use a proper layer instead of abusing the undo stack. This reduces the number of undo states created, and should make it easier to implement passive selections in the future. (Selections shouldn't create an undo state until you start dragging them.) This should also fix a bug in multiplayer where "inverty brush" could be left behind.
Isaiah Odhner