if you only want one opencv function I'd just write a "glue" function in c++ which takes in a haxe BytesData object and returns one, much easier than trying to extern all the of opencv classes you'd need to do it in haxe

yeahhhh i just need to know how to do that

again, the opencv file structure is shitty and i dont understand it

good thing there's a lot of examples / documentation out on the internet for opencv

its a pretty simple api to use

and theres near 0 documentation about writing glue code for haxe

and thats tthe part i dont know - how to connect the glue code and haxe

Can I change a slider value scale?

@limited-rose-72431 can you maybe help me with that in a VC?

what do you mean "scale"? Like min/max?

i found a bug: tooltips should be created on top of everything

is that a tooltip for a menuitem?

yes

suggestion: make the dataSources recive an

EitherType<Dynamic, Item>

, Item being a typedef with all of the accepted values for the views

its backwards compatible (haxe 3.2) and wont do anything other then add a type safe alternative

why wouldnt you just use

ArrayDataSource<Item>

?

why array?

Because DataSource itself doesnt store anything, if you are creating a new instance that will actually hold something it will have to be ArrayDataSource or ListDataSource

i ment this: change the function of DataSource:

haxe
function add(item:Dynamic) {}

to

haxe
function add(item:haxe.#if haxe4 ds #else extern #endEitherType<Item, Dynamic>)

wait im confused

u should defo document that

except the actual function signature is

public function add(item:T):T

Wait, im super confused

...

don't have time right now to put together a full example, but very quickly this is what the glue function might look like

cpp
Array<hx::Anon> hx_hough_lines(Array<uint8_t> in_image)
{
    auto base   = in_image->base();
    auto input  = std::vector<uint8_t>(base, base + in_image->length);
    auto output = std::vector<Vec2f>();

    HoughLines(input, output, 1, CV_PI/180, 150, 0, 0 );

    auto anons = Array<hx::Anon>(0, 0);
    for (auto&& vec : output)
    {
        auto anon = hx::Anon_obj::Create();
        anon->Add(HX_CSTRING("x"), vec.x);
        anon->Add(HX_CSTRING("y"), vec.y);

        anons->Add(anon);
    }

    return anons;
}

(thrown together from the opencv hough lines example and past use of opencv, may not work as is, will probably need changing to fit your needs, etc, etc) and on the haxe side the extern would look like

function hx_hough_lines(input : BytesData) : Array<{x : Float, y : Float}>;

that looks like black magic (i dont know cpp)

if you don't know cpp you're not going to have a good time writing externs for the cpp target

precisely

btw, there is no min, max attributes being set in the examples page

yeah, fair enough - there are certainly a bunch of properties to play with on sliders: http://haxeui.org/builder/?oanfqv