https://linen.dev logo
Powered by
# haxe-ui
  • b
    i think that would be all you would need to set pixels on the raw data
  • b
    unless getData also returns a copy (though i dont see why it would)
  • o
    so just iterate over them each side of rendering
  • b
    Copy code
    unsigned char* wxImage::GetData    (        )    const
Returns the image data as an array.

This is most often used when doing direct image manipulation. The return value points to an array of characters in RGBRGBRGB... format in the top-to-bottom, left-to-right order, that is the first RGB triplet corresponds to the first pixel of the first row, the second one — to the second pixel of the first row and so on until the end of the first row, with second row following after it and so on.

You should not delete the returned pointer nor pass it to SetData().
  • b
    so yeah, its as expected
  • o
    ok it's rgb, need to look into pixels to see what it provides, it seems to have UInt8Array in PixelsData
  • o
    shame you can't do ARGB but you could perhaps emulate by using previous value...
  • b
    there is also getAlpha
  • b
    Copy code
    unsigned char* wxImage::GetAlpha    (        )    const
Returns pointer to the array storing the alpha values for this image.

This pointer is NULL for the images without the alpha channel. If the image does have it, this pointer may be used to directly manipulate the alpha values which are stored as the RGB ones.
  • o
    Well feel free to pull against the concept but likely need to park it for now. Need coffee and to feed cats, not sure I can spend the day fighting with pixels 🙂 But it's setup ready for next time.
  • b
    whilst working on steppers added an "option-stepper"
  • o
    @User I was just thinking, even though did not want to spend today on bytes! This method in hxWidgets.hx.Image provides only private access to the image, so I will likely be stuck next time.
    Copy code
    Haxe
    private var imageRef(get, null):Pointer<WxImage>;
    private function get_imageRef():Pointer<WxImage> {
        return _ref.reinterpret();
    }
    but there is no access route via hx.Image. Really there needs a property rgbArray and alphaArray and perhaps even rgbPixel and alphaPixel for individual access.
    Copy code
    Haxe
    public var rgbArray(get, set):Array<UInt8>;
    inline function get_rgbArray():Array<UInt8> {
       var p =  this.imageRef.getData();
       var l = Std.int( this.width() * this.height );
       return [ for( i in 0...l ) p[ i ] ]; // or similar.
    }
    inline function set_rgbArray( v: Array<UInt8>):Array<UInt8> {
       var p =  this.imageRef.getData();
       var l = Std.int( this.width() * this.height );
       for( i in 0...l ) p[ i ] = v[ i ];
       return v;
    }
    Still confused to understand how Alpha would relate to UInt8, would alphaArray be best defined as and just convert it within the function to be most compatible with normal use. if you think it would work, I could pull the rgbArray but suspect to actually test it maybe extra.
  • o
    Also I think it would be ideal to provide abiliy to easily create an empty Image, something like..
    Copy code
    Haxe
        public static function createImage( w: Int, h: Int, rgb: Null<Int> = null, alpha: Float = 1., isAlpha: Bool = false ){
        var l = Std.int( w*h );  
        var hasAlpha = Bool( alpha != 1. ) || isAlpha; 
        // very unsure on this part or anything bytee!
        var bytes = ( hasAlpha )? Bytes.alloc( l ): Bytes.alloc( l << 2 );
        var stream = hx.widgets.MemoryInputStream( bytes );
        var image = new Image( stream );
        // initialize color 
        if( rgb != null ){       
           image.rgbArray = [ for( i in 0...l ) rgb ];
           if( hasAlpha ) image.alphaArray = for( i in 0...l ) alpha );
        }
        return image;
    }
    Thoughts... I am not sure I have hxWidget setup on mac and setting up test maybe tricky but think this maybe required for image manipulation.
  • o
    Really not worth me trying to draw in Images if I can't access the getData stuff?
  • b
    there are two sets of classes, the externs (wx.\*) and the wrappers (hx.\*)
  • b
    i would ignore the wrappers for now
  • o
    well adding these to the wrapper adds a nice interface...
  • o
    I am not really sure how to create a new wx.Image
  • o
    without the wrapper
  • b
    yeah, its a valid point... i thought in your Main.hx you were using the externs directly... but you arent
  • o
    well yer coffee helps thoughts 🙂
  • b
    getData would need to be exposed, but that doesnt make sense for the wrappers as you should never need to deal with pointers directly
  • o
    sure my rgbArray provides getter setter for the getData
  • o
    on hx.Image
  • o
    so hides exposure
  • o
    I think Array is fairly easy for externals apps to deal with.
  • b
    for now anyway, you could just do 
    var p = @:privateAccess myImage.imageRef.ptr.getData()
  • o
    does allowing private still work outside the package?
  • b
    yeah, pretty sure that should work
  • b
    i dont see how the array is going to work though, it would need to be a copy of the bytes, and that makes it pretty useless
1...881882883...1687Latest