https://linen.dev logo
Powered by
# haxe-ui
  • c
    Then I have another feature request if parsing is that robust : could the compiler throw a pointer when facing broken XML ?
  • c
    Now it throw "defined in this class" but it doesn't tell which xml is broken.
  • b
    how are you using the xml's? Custom components?
  • c
    Might not be needed anymore with the new nesting but could be usefull I usually go to an online xml linter
  • c
    XML
  • b
    and when you say "broken xml" what do you mean exactly?
  • c
    (i am using XML)
  • c
    I mean non conformant
  • b
    doesnt haxe already throw an error in that case?
  • b
    Copy code
    C:\SDK\haxe\std/haxe/xml/Parser.hx:243: characters 7-12 : Uncaught exception haxe.xml.XmlParserException: Duplicate attribute [style] at line 2 char 20
C:\SDK\haxe\std/haxe/xml/Parser.hx:117: characters 2-30 : Called from here
C:\SDK\haxe\std/Xml.hx:122: characters 9-35 : Called from here
C:\Work\HaxeUI\haxeui-core\haxe/ui/parsers/ui/XMLParser.hx:15: characters 22-37 : Called from here
C:\Work\HaxeUI\haxeui-core\haxe/ui/parsers/ui/XMLParser.hx:74: characters 38-104 : Called from here
C:\Work\HaxeUI\haxeui-core\haxe/ui/parsers/ui/XMLParser.hx:29: characters 12-68 : Called from here
C:\Work\HaxeUI\haxeui-core\haxe/ui/parsers/ui/XMLParser.hx:49: characters 20-69 : Called from here
C:\Work\HaxeUI\haxeui-core\haxe/ui/parsers/ui/XMLParser.hx:49: characters 20-69 : Called from here
C:\Work\HaxeUI\haxeui-core\haxe/ui/parsers/ui/XMLParser.hx:49: characters 20-69 : Called from here
C:\Work\HaxeUI\haxeui-core\haxe/ui/parsers/ui/XMLParser.hx:20: characters 8-56 : Called from here
C:\Work\HaxeUI\haxeui-core\haxe/ui/macros/ComponentMacros.hx:115: characters 30-132 : Called from here
C:\Work\HaxeUI\haxeui-core\haxe/ui/macros/ComponentMacros.hx:87: characters 8-104 : Called from here
  • b
    i see, but no xml filename there, is that what you mean?
  • c
    Yep !
  • b
    gotcha, ill have a look - i would guess haxe makes this easy, but dunno
  • h
    noticed sliders don't get correctly colored when displayed with 
    direction="vertical"
    in haxeflixel
  • h
    horizontal
  • h
    vertical
  • h
    I'm referring to the blue color, the white in the second pic is unrelated to the ui
  • b
    doh, oversight... fixed in haxeui-flixel git
  • h
    thanks a lot! fast as ever
  • b
    one liner... well, two liner 😄
  • u
    is there a way to get a label to have its text centred vertically
  • u
    how do I use 
    ComponentEvents.registerEvent()
    ? I cannot find anything about it on the docs
  • u
    never mind I figured out what I was trying to do
  • b
    all sorted then? 🙂
  • u
    is it possible to make a component centred (horizontally) inside its parent (preferably from xml)?
  • c
    Hey Ian,
    Copy code
    hx //ComponentMacros.buidComponent 
macro public static function buildComponent(filePath:String, params:Expr = null):Expr {
        var builder = new CodeBuilder();
        try{
            buildComponentFromFile(builder, filePath, null, MacroHelpers.exprToMap(params), "rootComponent");
        }
        catch (e:Exception)
        {
            throw new Exception('Parsing error in $filePath', e);
        }
        builder.add(macro rootComponent);
        return builder.expr;
    }
    Seems to do the trick but as I am a noob with the framework (and not macro virtuoso) I cannot asses the side effects.
  • b
    oh, nice one, ill paste it in and see... looks fine though, thats basically what i was looking to do essentially
  • b
    ie, catch the error and "enrich" it
  • c
    Yes shouldn't do more harm
  • b
    do you know when haxe.exception was introduced?
1...561562563...1687Latest