its personal preference i guess, and i tend to follow source better than docs (also docs can be out of date, source cant be)

its mostly out of laziness (outdated docs), whne i change stuff i just update the docs with a couple of words

like changing params, return types etc.

> mostly out of laziness 100% - thats absolutely my excuse / reason - if its a choice between writing haxeui or documenting haxeui - well, i think my choice is obvious (as bad as that choice is)

about that, how do i set the color of the text?

color should work, but i dont think 0xRRGGBBAA is right, just 0xRRGGBB

btw did you notice that lime git has docs😳

i installed git for the

FileDialog

hl fix and noticed they added documnetation

see above about how i dont read docs 🙂 - so no, hadnt noticed, didnt even know what the "old" docs looked like

there were no old docs

i think anywhere

(also, i dont really use openfl very much, its an important backend, but not one i use for anything personally)

i havent even once seen docs on lime fields/methods

just noticed that styles are not applied to menus and colors arent applied to borders

?

It probably makes more sense to use haxeui css for things like menus, since there are different states you'd want to style - that said, i would have expected color / borderColor to work (for the "default" state), so ill have to check it out

eg: https://github.com/haxeui/haxeui-core/blob/master/haxe/ui/_module/styles/default/menus.css

obviously you wouldnt have to override all of them, but just saying how its not as simple as "background / foreground" colour

so yeah, this doesnt work (and i would have expected it to):

xml
    <menu-bar>
        <menu text="Menu 1">
            <menu-item text="Item" />
            <menu-item text="Red" style="color: red;" />
            <menu-item text="Green" style="color: green;" />
            <menu-item text="Blue" style="color: blue;" />
        </menu>
        <menu text="Menu 2">
            <menu-item text="Item" />
        </menu>
    </menu-bar>

OK, should be fixed now (latest haxeui git)

(again, this will set things on the default state, if you want to change things like hover colors etc - ie, "state" - then you need to use css)

fyi, there are various ways to add css styles in haxeui, but since you prefer to use code (it seems), you might want something like:

haxe
        Toolkit.styleSheet.parse(".menuitem:hover {
            background-color: red;
        }");

abstracted "canvas" drawing api might be making its way into core sooner rather than later... the test worked out better than expected 🙂

i noticed that hashlink has some graphics stuff included in it by default

are there any plans to have a haxeui backend that uses them?

what graphics stuff does HL include?

right, fair enough, well, no - no plans for a HL backend... at least not at the moment

idk why you need that kind of backend lol...

same

it's also real low level