https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • c
    guess haxe-rs is gonna have at least one more use too
  • b
    @full-journalist-82607 - btw, i think im going to go a slightly different direction in the "USER_SUBMIT" stuff (although obviously i appreciate the PRs) - your wx PR is especially useful since i didnt realise we'd need a different constructor flag - but for composites, i think we can do it all in core TextField... that way all (composite) backends benefit without changes
  • f
    It is indeed simpler 🙂 I knew you had some thing in mind as weren't pulling my PRs 😉
  • b
    heh heh, well, tbh, i hadnt even thought fully about it, but when i saw the PRs (for composites) i thought "hmmm, core can do this"... but the wx PR was defo enlightening... I think for wx we'll just always pass that flag... i mean, i cant see any reason why not
  • b
    oh, yeah, you already have done that
  • b
    OK, so actually, i got it wrong, you dont need to pass anything special into the native control constructor?
  • b
    sorry, yeah we do
  • b
    style |= TextCtrlStyle.PROCESS_ENTER;
  • b
    not the constructor, but yeah, not reading properly 🙂
  • f
    Haha, it's still morning !
  • b
    indeed 😄
  • f
    Yeah, just saw you acceptet the pop menu PR 🙂
  • b
    yeah, and the user submit one for wx... that one will need to be handled by the backend since its quite specific to wx
  • f
    I'll leave you to work on ... forms ? Hmm, nice 🎁
  • b
    yeah, well, im working on the submit now.. the idea being you can do:
    Copy code
    xml
    <form onUserSubmit="...">
        <label text="Username" />
        <textfield />
        <label text="Password" />
        <textfield />
    </form>
  • b
    simple stuff, but something ive personally wired up manually like 20 times in the past
  • f
    Yeah this will be quite useful. I think I'll use them as you as soon as you commit it lol
  • b
    im also thinking to go back to "SUBMIT" also, i defo like it more, and as !billy said, the "user" part is inferred... if we need to change it, so be it.. but i defo think submit is nicer
  • b
    ill let it sink in, wont make any changes until "morning brain" wears off 😄
  • f
    Only half an hour left and your brain will be functional !
  • b
    already liking it 🙂
  • b
    Copy code
    haxe
@:xml('
    <form>
        <label text="Username" verticalAlign="center" />
        <textfield id="username" />
        <label text="Password" verticalAlign="center" />
        <textfield id="password" />
    </form>
')
class MyForm extends Form {
    public override function validateForm(fn:Bool -> Void) {
        var invalidFields = [];
        if (username.text == "") {
            invalidFields.push(username);
        }
        if (password.text == "") {
            invalidFields.push(password);
        }
        for (f in invalidFields) {
            f.shake().flash();
        }
        fn(invalidFields.length == 0);
    }
}
  • b
    easy 🙂
  • b
    ... and now the important question, which looks better / more correct for a "default" button:
  • b
    or
  • b
    ... ... ... im torn
  • p
    I'd say the second one, because it's more visible that there's something special about it?
  • b
    yeah, i think i agree... i just worry that its a little too obvious? I try not to add too much colour to the default theme so its a little more flexible... dunno
  • p
    Hmm, looks like windows just does a blue border and leaves the blue fill for hovering over a button.
  • p
    (And with "windows" I mean whatever thing they're using for the Explorer UI nowadays)
1...139513961397...1687Latest