Brendan Duncan
Brendan Duncan
You're right, I typed that without fully thinking it through. I can add as* helper methods to Image to reduce the boilerplate code.
Actually, I believe with the ByteBuffer.as* methods, offset and size are optional and will be full views of the data without them specified...but I'm not at the computer now to...
Just checked and they are optional and will be full view of the buffer without being specified, https://api.flutter.dev/flutter/dart-typed_data/ByteBuffer/asUint32List.html. It just requires the buffer lengthInBytes be divisable by the elementSizeInBytes (4...
Nice PCanvas library, by the way.
True, but in this case buffer is always at 0 offset. Either way works.
Image.numChannels will be 4 if it has alpha, or 3 if it doesn't. I could add a `Image.hasAlpha` property to help clarify that. The Image.convert method can add/remove an alpha...
I'll add a 3.x migration doc, too. So much to do.
Sorry I haven't been able to respond to reports recently. Something I never got to with the Command API is adding a way to process a single frame from a...
I'll see if I can add a luminance option to getBytes again, sorry for the breaking change. The equivalent without that would be something like: ```dart final imgRgba8 = image.convert(format:...
I have nothing more to suggest. What I suggested already would produce image data the same as it was in v3. If your printer thing needs a monochromatic binary image,...