https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    true enough, flash is a supported platform, and i dont think the joke, comment, whatever you want to call it says anything about that...
  • q
    Yeah, that's fair enough, at least.
  • b
    its the equivelent of:
  • b
    which is thrown around in the teams i work with all the time... in jest
  • q
    Yeah, I don't know.
  • q
    And here, it's not "I don't get it was meant as a joke" at this point (to say it a third time)
  • b
    is it the correct response to an issue? Maybe not, but again, this was in a chat, not on a "formal" GH issue
  • q
    It's "maybe that - yeah, this.
  • q
    Well, which one? I can easily drop issues in either place.
  • q
    We wound up in discord eventually anyway, so it seemed "well enough".
  • b
    issues make sense for issues, and if a GH issue had a "works on my machine" it doesnt make much sense... a forum post? chat? Sure... why not
  • q
    Fine, then let's change the way I'm addressing this, since I'm clearly botched in that regard. I'mma at least raise "uh, WTF" in chat, but actual write ups I'll submit to github. Does that work better?
  • b
    makes total sense to me... issues are the formalisation of problems... discussions there are generally technical and to the point, chat / forum posts about issues arent... thats my feeling anyway
  • q
    Okay. Noted.
  • q
    In the meantime, that issue may be legitimate. While it's true I prefer to keep in motion, as a general rule I don't rush upstream if I can avoid it. I've been watching a fight between MelonDS and Dsemume that is probably going to become my teaching example on "don't disregard possible, tangible issues for personal reasons" so... I'm an asshole (if that's the assessment), the problem may be legitimate and should still be looked at, and uh... get back to me on that.
  • q
    And a note to self that I left leadership and management instruction years ago for a reason, stop talking like that >.<
  • f
    i want to add component to a vbox with a for loop but it doesn't work
    Copy code
    Main.currentView = ComponentMacros.buildComponent("assets/ui/home.xml");
        for ( news in Json.sampleNews.news ) {
            var box:VBox = Main.currentView.findComponent("sample");
            var title:Label = new Label();
            var author:Label = new Label();
            var content:Label = new Label();
            title.text = news.title;
            author.text = news.author;
            content.text = news.content;
            try {
            box.addComponent(title);
            box.addComponent(author);
            box.addComponent(content);
            } catch (err:Dynamic)
            {
                trace(err);
            } }
            Screen.instance.addComponent(Main.currentView);
    i receive Invalid field access : addComponent . Am i doing something wrong ?
  • q
    Cast the box.
  • q
    var box:VBox = Main.currentView.findComponent("sample", VBox);
  • f
    :/ i still receive the same error
  • q
    Probably beyond me, if you replaced that line with the one I gave you.
  • q
    Sorry.
  • q
    Wait. Can I see your XML, please?
  • f
    Copy code
    <?xml version="1.0" encoding="utf-8"?>
<tabview width="100%" height="100%" styleNames="body">
    <style source="../css/main.css" />
    
    <vbox text="home" styleNames="main">
        <label text="news" styleNames="title" />
    </vbox>
    <vbox text="delete news" id="sample" styleNames="main">

    </vbox>
    <vbox text="add news"  styleNames="main">
        
    </vbox>
    
</tabview>
  • q
    Hmmmm... Ponderous. I had thought perhaps there was a subtle issue there in type mismatching or even case. Nope. I'm sorry I'm pretty useless here. On the bright side, that should be plenty enough once someone more capable gets here.
  • b
    hi @fierce-restaurant-45913 - indeed strange, lemme try it out in a test app
  • b
    not that this should matter, but what backend?
  • b
    ah
  • b
    actually, i can see whats happening
  • b
    sample is a tabview page, which means it isnt created yet... is this new component method branch? I feel like there is a fix there for it
1...535455...1687Latest