https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    but then CI picks them and they are easy enough to change
  • b
    ie, im not using some "killer feature" from haxe4
  • r
    What is the purpose of compiling them to Haxe? Consoles?
  • p
    I have a tableview based on ArraySource.. I want to update 1 item in the arraysource and have the tableview display the change. Do I have to reset the datasource?
  • f
    I don't think so
  • f
    oh sorry misunderstood, I have to think
  • f
    If you use the update function, you won't need to
  • b
    you can also use 
    implements IDataItem
    in the class (if you have one) and then changing any field on that will update the datasource (and therefore the table)
  • b
  • p
    ok, thanks
  • p
    Here is a weird one. The dialog, called in mainview, isn't visible? Its behind the background color. http://haxeui.org/builder/?49ff3274
  • b
    i think you are probably calling it a little too early
  • b
    "new" gets called pretty instantly, so you are adding the dialog, which adds it to the screen, then, at a later point in time the main component initializes and add itself to the screen
  • b
    you can see this is the case if you change the background opacity:
  • b
    > Its behind the background color. oh, you already knew that
  • b
    the solution is quite simple, just move your dialog create into an onReady handler which is called after the component is initialized, measured and added to the screen
  • b
    Copy code
    haxe
@:build(haxe.ui.ComponentBuilder.build("assets/main-view.xml"))
class MainView extends VBox {
    public override function onReady() {
        super.onReady();
        Dialogs.messageBox('Going Inn:', 'No Error', 'error');
    }
}
  • b
    for clarity, something like this is happening:
    Copy code
    haxe
var m = new MainView(); // <--- dialog is being created here and added to screen
Screen.instance.addComponent(m);
  • p
    That was the answer. My actual issue was an alert for an http error but the request and alert was in the "new". Thank you
  • f
    Hmm, interesting, with the new htmlText, on hxWidgets, when label.htmlText = " {{GENERAL_FEEDBACK}} "; // here there's a segmentation fault label.htmlText = " General Feedback "; // this works But it seems that the exact same text is transmitted to ctrl.setLabelMarkup(normalizeText(_value)); when I trace the text in normalizeText. I even traced the charCode for each letter ! I don't see any difference
  • b
    i wonder if {{}} means something to wx
  • b
    oh, you are saying it already did the replacement
  • f
    But the weird thing is that it seems that {{}} isn't even transmitted to setLabelMarkup
  • b
    gotcha
  • b
    have you run as debug? Any stack trace?
  • f
    I thought it was a weird unseen character somewhere
  • f
    #0 0x00005555561e4f44 in hx::widgets::Control_obj::setLabelMarkup(String) ()
  • b
    got a full(ish) test app, with all the resources and strings, etc? ... i can run this end
  • f
    Going to make a test app 🙂
  • f
    I'll send it to you tomorrow, it seems that there few more nuances ( setting the text after or before the creation of the component)
1...136613671368...1687Latest