https://linen.dev logo
Powered by
# haxe-ui
  • b
    sounds good... the next release (1.3) will concentrate on native mobile, ie, haxeui-android, and thanks to you, possibly haxeui-ios
  • b
    That would be nice 😄 with libclang now somewhat working this might be a better way for me to parse UIKit etc and generate externs
  • b
    (If all you have is ammer, everything looks like a native library)
  • b
    i havent actually played with ammer yet, but seems nifty
  • p
    That's a known issue with heaps and haxe 4.2. Heaps only works with pre 4.2 or 4.2.1.
  • m
    textfield in heaps was working fine as of Saturday but I haven't upgrade to Haxe 4.2 since there are still issues with it
  • m
    @User justing pinging you on flixel-backend mobile support, any news? (no pressure 😋 )
  • b
    Is mobile not supported? I assumed it would just happen
  • m
    It is, but doesn't currently compile because there's no code to handle touch input, only mouse events which are not defined in mobile targets
  • b
    Oooohhhh
  • b
    yeah, ill get to it certainly - not 100% sure when though - im off from friday to tues
  • c
    Hi ! I am trying to add a parser for localization. When i try to register it in my app by
    Copy code
    hx
LocaleParser.register("myExt", MyClassExtendingLocalePArser);
    The app breaks silently (blank page on compile). though if I register it in the
    Copy code
    hx
//LocaleParser line 32
private static function defaultParsers() {
        if (_parsers == null) {
            register("properties", PropertiesParser);
            register("po", PoParser);
            register("myExt", MyClassExtendingLocalePArser);
        }
    }
    It works fine, would that be the only way to add a custom parser ?
  • b
    ill have to check, certainly you should be able to register it outside the defaultParsers...
  • b
    though i havent actually tried that
  • h
    what's the difference between a normal and virtual list? I noticed the virtual seems to be much faster
  • b
    virtualisation for lists / tables means that they reuse items renderers, so if your list can only display, lets say 8 items, then only 9 item renderers will be created and they will be resused for, potentially, millions of data items
  • b
    (ie, its the data the scrolls, not the items in the view)
  • h
    is there any drawback from reusing item renderers?
  • b
    i think there is only partial support for variable height item renderers
  • b
    but if your item renderer is always going to be the same height then not really
  • b
    maybe scrolling is a little worse? Though i might have fixed that ages ago
  • b
  • b
    yeah, scrolling isnt as nice - honestly, i thought that was fixed - maybe its on a list that i didnt get around to
  • h
    no worries and thanks a lot for explaining this!
  • b
  • b
    defo used to work
  • b
    so ive broken something
  • i
    how do I make, say, a button in a haxeui app run a function I've declared somewhere? The examples have onclick properties with code inside them, but I can't get them to run a function available in the same .hx file that creates that app -- repost because I am blind and didn't see this channel before
  • i
    the hello world code, for example, has 
    <button text="Click Me!" onclick="this.text='Thanks!'" style="font-size: 24px;" />
  • i
    but if I change the 
    onclick
    code to try to run a function I've declared in the same source file that runs that UI (i.e. 
    onclick=myFunction
    ), it can't run it
1...583584585...1687Latest