well this is rendered to png in neko.

I should probably update so the fills work, but concept is that if I have Array access to the Image I can draw on it.

no toolkits just format and neko and some of my code to help

am I missing your point?

hxPixels is ideal in providing a generic wrapper for pixel manipulation, perhaps it could be improved. pixelDrawing is probably a rather bad port of just what I needed from http://members.chello.at/~easyfilter/bresenham.html

stuff we worked on for hxDaedalus.

the array access could allow other frameworks access to wx images.

@:native("GetData") public function getData():RawPointer;

Could we translate this as haxe.io.UInt8Array ... mm

likely that would be enough to draw easily on it.

If you have a demo project with this setup then... we can draw...

is there a way to do drag and drop files

there is a sample in wx I saw but no idea if implemented

ok so with getData, I get the start of the data set and then somehow to extract an array I need to increment the RawPointer by Utf8 length until width x height.

there isnt currently, no

You should just be able to use array access no?

Ian I have roughed out the concept it would not currently have antialias. https://github.com/nanjizal/cornerContourWX/blob/main/src/Main.hx Need to sit down and do some messing with Bytes stuff to see what works and get your samples to run locally. Not sure can commit to that today that bytes stuff normally blows my mind. But thought roughing out the structure before some breakfast coffee would be worthwhile. I added pixel support to cornerContour https://github.com/nanjizal/cornerContour/blob/main/src/cornerContour/drawTarget/PixelDraw.hx note plot is AA but fill currently is not so if stuff can be made to work could look at AA fill approaches or perhaps better to try to an AA edge filter. may well do a pull soon for ceramic, kha, heaps to Pixels had some proposed code but need to consider and double check.

pretty sure that wouldnt work... or even compile

yer I need to look at all the bytes stuff.

getData would return a pointer to the actual memory that contained the data, not a haxe bytes class... there may be a function to convert it, though i suspect if there is it will create a copy

I am unsure on image setpp

the copy aspect is why I thought there would be convert from and to required

although actually, looking at the rest of the code, if it were a copy it wouldnt matter i guess

i thought you wanted to set bytes there and it set the bytes in the getData pointer

but i see thats not the case?

I feel if I can use Pixels and just get/set the raw pointer from them that would be ideal. Pixels allows generic approach for toolkits and likely does not add much overhead.

by adding drawPixels to cornerContour I am actually also targetting js, swing, openfl, etc... for bitmap stuff

well, you should defo be able to get / set the raw pointer data

haxe
var p = image.getData()
var i = p[n];
p[n] = i;