https://linen.dev logo
Powered by
# haxe-ui
  • o
    I had problems with private I thought they broke i
  • o
    it
  • b
    i use it all the time to test things out
  • o
    I have a setter as well
  • o
    that should workL
  • o
    work?
  • o
    inline function set_rgbArray( v: Array):Array { var p = this.imageRef.getData(); var l = Std.int( this.width() * this.height ); for( i in 0...l ) p[ i ] = v[ i ]; return v; }
  • b
    none of that seems a straight forward as just somehow wrapping the pointer itself for direct access rather than copying arrays back and forth
  • o
    so you mean like an abstract over the rawPointer
  • b
    yeah, something like that
  • b
    i mean, in reality the raw pointer would be 100% fine here, it does everything you need, but i dont like exposing pointers in the wrappers
  • b
    but maybe this is a special case tbf
  • o
    abstract ( { pos: Int, rawPointer } )
  • o
    well drawing on an image does allow users to draw svg paths
  • b
    yeah, tbh, im kinda edging toward actually just exposing the raw pointer here... i mean, its is a special case, and wrapping it is just overcomplicating it for no reason
  • o
    so it provides a low level hook
  • b
    and abstract wrapper over a pointer just so the wrappers arent returning a pointer (even though they still would be) seems dumb
  • b
    and in reality, when i say "Image.getData" i would expect a raw pointer... i mean, thats what the data is
  • o
    the problem is that raw pointers are not really what haxers are used to using I presume cpp has Pointer or something to make it cleaner
  • o
    or ...
  • b
    i dont think using a pointer makes it any cleaner
  • b
    i would also argue that if you dont know what a pointer is then you probably shouldnt be working with the memory internals of an image... ... i mean, i guess
  • o
    the problem is that user can write beyond the end?
  • b
    yeah, but this is a real edge case, i mean, the getData is anyway
  • b
    so yeah, you can nuke things if you are being dumb, but why would you want to access the raw data (as a pointer) unless you had some idea about what you were doing in the first place
  • b
    i guess one benefit of an abstract is you could build a nice(er) api for it, like 
    image.data.set(x, y, colour)
  • o
    abstract hxWidget.hx.Canvas( hxWidget.hx.Image ) would work ?
  • o
    then you can add some other stuff later
  • o
    if you want
  • b
    i was thinking more an abstract around the pointer than is returned from getData
1...882883884...1687Latest