https://linen.dev logo
Powered by
# haxe-ui
  • p
    The objectMap impl for js uses `__id__`:
  • h
    damn this is so sexy I love it, have been trying to implement it on my website without luck, maybe I should make it in haxeui...
  • h
    by the way, does anyone know how to automatically resize a `ListView`'s width based on the width of its contents?
  • h
    I'm filling in a listview with floats at runtime and I don't like when the text overflows and wraps
  • b
    hmmm, was hoping width:auto would work, but doesnt seem to... ill take a look when i get a moment
  • r
    The excel type control would be nice to have on all platforms. (wxGrid)
  • m
    @User This _themes.get(themeName); is returning NULL in the buildThemeEntries function in haxeui-heaps. Where is the getter for Theme? I'm thinking the resources aren't loaded
  • b
    agreed, its in hxwidgets now, so adding it to haxeui-hxwidgets shouldnt be hard... creating a composite counterpart could be a pain though, but i think something very doable
  • b
    hmmm, ill have to check it out... is this with a custom theme? Or just the inbuilt ones?
  • b
    nice, so linking up a native tableview (wxDataViewListCtrl) was actually nice and straight forward 🙂 Composite:
  • b
    native:
  • b
    not totally done... and still a very preliminary impl, but worked out nicely 🥳
  • m
    @User It decided to work this morning after a reboot - custom theme is getting hung up - I'll keep plugging along and let you know
  • b
    so it magically decided to work?
  • m
    last night the get was returning null. even when I commented out the custom theme. Toolkit.theme did report the custom theme name. When I restarted just now with the custom theme commented out, all the traces started showing the default theme parts. Hashlink is hanging up somewhere either way though so I'm slogging thru to find out why. on the plus side, I got ComponentMacros to build and show a screen yesterday but not so far today.
  • m
    OOOOKKK - even more weirdness - I put a breakpt in at theme and now the tarces work
  • b
    component macros should work fine... you getting any errors? Have you tried a simple base project in heaps to isolate? (keep in mind at the moment you'll probably need to call .ready())
  • b
    im going to look at haxeui-heaps later tonight hopefully and get these changes squared away
  • m
    It may be related to haxeui-core git version. I discovered that I was using the haxelib version earlier last night and switched to the git version in the compile.hxml. Resources don't seem to be loading right yet. I'm looking at it on the haxelib version. I have cloned the haxeui-heaps so I could work on that
  • b
    ok, you almost certainly want to be using the git versions...
  • b
    haxelib is so far behind at this point
  • m
    yeah - i know - but it is the one that seems to work with haxeui-heaps
  • m
    Copy code
    Toolkit.init({app:instance, manualUpdate:false});
        var mScr = ComponentMacros.buildComponent("res/test.xml");  
        fui = new h2d.Flow(s2d);
        trace("After flow. mScr: " + mScr);
//        var font = Res.font.Avdira.toFont();
/*
        var tf = new h2d.Text(hxd.res.DefaultFont.get(), fui);
        tf.text = "hello!";
        var bmp = new Bitmap(Res.img.hong_kong.toTile(), fui);
*/
//        fui.addChild(b);
        haxe.ui.core.Screen.instance.addComponent(mScr);
  • m
    just in case you need it to get it to work
  • m
    took me a bit to figure out I needed to put opitions in
  • m
    I had to do it that way because the HaxeUIApp wasn't working for me under heaps
  • m
    could have been my ignorance
  • b
    ok, and you didnt need the ready because you used screen
  • b
    ill hopefully have some changes a little later to clean some of this up
  • b
    so, just to confirm, the git version didnt work and haxelib version did?
1...527528529...1687Latest