Hey Ian, did you see enough of coconut + haxeui to have an idea what is going wrong with coconut + haxeui-hxwidgets that would cause render to not be called on state change? With code that was working with heaps backend =/

hmmm, no idea to be honest... does coconut, internally, constantly destroy and recreate components?

(i still havent actually played with coconut as of yet... keep saying "today" and then "tommorrow" :/ )

I don't think so, and if render is not called it doesn't have a chance to do so (unless that's the root node that fails.. hmm will see if I can do something there)

If I call Renderer.updateAll() manually it works °°

hmmm, right... im not sure how things work internally, it seems strange that this is something that works on heaps but no wxwidgets... i would have expected them to behave the same?

yeah.. well at least I can add manual calls and go on with my tests

Maybe Juraj will know what's wrong

@User Just got the hxWidgets showcase example to compile with GCC on Windows 😄

you have to compile wxWidgets with GCC, and edit the Build.xml file a bit, but it works

oh yeah? I compile on linux all the time... what changes did you have to make?

1. Followed these instructions to compile wxWidgets with mingw: https://wiki.wxwidgets.org/Compiling_wxWidgets_with_MinGW 2. Added these to hxWidgets's `Build.xml`:

<set name="lib_folder" value="gcc_lib" if="HXCPP_MINGW" />
    <set name="lib_folder" value="gcc_dll" if="HXCPP_MINGW" />

Those are the folders the libraries get created at if you compile with GCC. 3. Changed this on the linker part of `Build.xml`:

<lib name="${WXWIN}\lib\${lib_folder}\*.lib" unless="HXCPP_MINGW"/>
            <lib name="${WXWIN}\lib\${lib_folder}\*.a" if="HXCPP_MINGW" />

Change the extension if you're using mingw. 4. Changed these on the

WXSTATIC

section of the linker part:

<flag value="/NODEFAULTLIB:LIBCMT" unless="HXCPP_MINGW" /> <!-- should remove this if using /MT but couldnt see an easy way -->
                <flag value="/MANIFEST:EMBED" unless="HXCPP_MINGW" />
                <flag value="/SUBSYSTEM:windows" unless="debug||HXCPP_MINGW" />
                <flag value="/ENTRY:mainCRTStartup" unless="debug||HXCPP_MINGW" />

Disable those if you're compiling with mingw. Then you can compile with

-D HXCPP_MINGW

in your hxml and it just works

> GCC on Windows didnt read the "windows" part

oh lol

cool stuff!

PR'able?

it looks pretty conditional what you listed

probably! I'll just try to reproduce it again in a VM to make sure I'm not forgetting anything

are the docs in a repo as well? I could add those details to the "haxeui-hxwidgets" setup guide (if you want to)

probably makes more sense to put them in the hxWidgets repo?

oh right, didn't realize there were build instructions there as well. I was just looking at the haxeui page

yeah, its a common misconception 🙂 hxWidgets has nothing to do with haxeui

haxeui uses hxWidgets to build a haxeui-hxwidgets backend

but hxWidgets itself can be used totally standalone (no haxeui)

i think, iirc, thats why someone PR'd: > hxWidgets is actually independent of haxeui-core (and haxeui-hxwidgets as well), and can be used on its own if you so desired (the showcase in this repo is an example of that). hxWidgets consists of two layers:

naruhodo

I messed with my environment quite a bit so I really want to reproduce this from scratch before submitting a PR but it seems to work fine

nice... starting to get rid of the hscript dependency... so script functions and handlers will be generated as haxe code at compile time, so something like this:

xml
<vbox style="padding: 5px;">
    <style>
        .button {
            font-size: 24px;
        }
    </style>
    <script>
        var a = 1;
        
        function testFunction1() {
            a++;
            trace("testFunction1 - " + a);
        }
        
        function testFunction2(param1) {
            trace("testFunction2");
            trace("param1: " + param1);
            trace("button1.text: " + button1.text);
        }
    </script>
    <hbox>
        <button text="Click Me 1111!" id="button1" style="color: red;" />
        <button text="Click Me!" id="button2" style="color: green;" />
        <button text="Click Me!" onclick="trace('bob222');trace('tim');this.text=button1.text;" style="color: blue;" />
        <button text="Click Me!" onclick="testFunction1();" style="color: blue;" />
        <button text="Click Me!" onclick="testFunction2('something');" style="color: blue;" />
    </hbox>    
</vbox>

Turns into generated code like this: https://pastebin.com/4TasGGk3

so many benefits to doing it this way...