Resolve #94 #95
Resolve #94 #95
Conversation
There was a problem hiding this comment.
Ok, so this seems like one of those opportunities to not add a lot of overhead to the already-congested startup sequence. In particular, we're opening, reading, and decoding the file, extracting just the width and height, and closing it, just to do it all again when we load it into the canvas.
It'll take a bit of restructuring, but it should be a lot more efficient to have resize-ivy-frame operate on a loaded bitmap file, and instead call it from elsewhere, after the image is loaded. Maybe an optional boolean param for load-image to control whether to call it or not?
- Avoid loading the image multiple times - Do not rely on pict library to determine scaling - Remove pict from main.rkt
|
@IonoclastBrigham These changes will allow it to reuse the already-loaded |
Seems to be operational on my end.