https://linen.dev logo
Powered by
# haxe-ui
  • m
    Does that impact anything else?
  • b
    not really much i can do about that since its an openfl thing
  • b
    in what sense? It removes all filters (shadows, etc) at the css parse level
  • m
    Oh, let me try
  • b
    haxeui_no_filters
  • b
    (not haxe, typo)
  • m
    I've built it with
    Copy code
    lime test cpp -debug -D haxeui_no_filters
    and it still happens
  • b
    sorry: 
    haxeui_nofilters
  • b
    should be 
    haxeui_no_filters
    really :/
  • m
    Now it worked
  • m
    There is something odd when I run with the xml like this... The wrapping box seems like part of the combobox
  • b
    you also need to change the .hx to extend HBox
  • m
    oh damn, obviously
  • b
    i did use to issue a warning, but i was getting false positives, so turned it off
  • m
    So for the moment I think I'll just wrap it with a box and move on
  • b
    yeah, until i have a chance to work out the weirdness, yeah... though for sure its a reasonable thing to do... so its a bug in haxeui (which ill fix)
  • m
    No worries! Thanks for the help! If you need any help testing stuff let me know
  • m
    I tried adding the dropdown to a box by code, still doesn't work...
  • m
    Only works if I add the box directly to it's xml it seems
  • b
    Copy code
    haxe
@:build(haxe.ui.ComponentBuilder.build("Assets/ui/xml/widgets_combo.xml"))
class DropdownTest extends HBox {
    public function new() {
        super();
        
        var dd = new DropDown();
        dd.dataSource.add("bob");
        addComponent(dd);
    }
}
  • b
    works for me
  • m
    oh but you added a DropDown created directly in code. What I did was, I have a root which is just a Box built from xml like you seem to have, and also a DropDown that is built from another xml being the root
  • m
    That seems to be the issue, having the dropdown as the root of a particular xml
  • b
    yeah, i mean, i doubt it has anything to do with the xml per se... there is something wrong with... well, i dont know, the dropdown being a top level component? (the xml just builds code, so if you are doing it in code its not a surprise you get the same strange behaviour as using xml)
  • b
    although
    Copy code
    haxe
        var dd = new DropDown();
        dd.dataSource.add("bob");
        Screen.instance.addComponent(dd);
    works fine... 🤔
  • b
    anyways, it'll be something dumb no doubt
  • m
    If that works, definitely it's small detail overlooked
  • b
    yeah, something small / silly
  • b
    OK, so i can see what is happening... when the top level component is an IDataComponent, the haxeui macros fail to build the data source
  • b
    so the same would happen with a listview also
1...106110621063...1687Latest