https://linen.dev logo
Powered by
# haxe-ui
  • c
    Actually come to think about it I dont really think openfl works with webgl
  • c
    I'm not too sure about the details but
  • c
    There are haxelibs for webgl
  • o
    I currently have... https://github.com/nanjizal/hyperKitGL/blob/main/src/hyperKitGL/Sheet.js.hx#L63 But either there or in my other stuff I am out by 2 since retina is 2x, so the mouse positions only work for me.
  • o
    Lime works with WebGL, but I don't know much about it's mouse stuff
  • o
  • c
    I'm not sure I can help you with this, sorry. I think someone else would be able to though
  • o
    so it has approaches for few targets in Lime it's bit ugly
  • b
    so @User - just reading up about flixel actions... havent played with them, just reading the docs... ... just so were on the same page... what exactly would be a use case for haxeui and actions? It feels like this is something that is specific to each app and not central to haxeui, but i might just be misunderstanding... can you give me a concrete use case so i can better understand?
  • c
    Actually, I don't think you're far from the truth. FlxAction is an input wrapper that combines mouse, keyboard and gamepad input all into one. Since controls for each project can differ significantly, you are right in that each use case would be different. The main problem I'm trying to figure out is how to get the two talking. And the main reason is because I'm not exactly sure how Haxe-UI Input is handled
  • b
    right, yeah, getting them talking may be a challenge - so maybe there can be updates in haxeui-flixel to make that easier... again, just so i can think about it and maybe come up with a demo can you give me a kind of solid, high level example of what you (or anyone) would use actions for in the context of haxeui? Ive never used actions so it would be useful to know in what sort of ways they are used (especially in the context of ui)
  • c
    A very similar situation is looked at in the flixel demo Cursor: https://github.com/HaxeFlixel/flixel-demos/tree/dev/UserInterface/Cursor This demo however uses Flixel-UI which uses it's own input handles, which also means it doesn't make use of FlxActions. The behavior I want with Haxe-UI and FlxAction is virtually the same but as I've been told Haxe-UI is a better UI solution than Flixel-UI, but it's major exception is it's input FlxAction currently is the best solution for input management as it effectively provides the best combination of input from multiple devices, personalized controls, dynamic control schemes and requires fewer lines of code
  • b
    ok, thanks for the info / example... ill let it percolate 🙂
  • c
    Hi there. Is there a "neutral" XML tag that I could use as root in sub xml resources ? I am trying to nest some xml definitions (mainly for reusability) that I would like import in a parent XML
    Copy code
    <import resource="assets/ui/common/nested.xml" />
    but that would contain siblings. Obviously if I put some siblings with no root around the parser will only grab the first node. Then adding root around the siblings yields a "Class not found". IOW :
    Copy code
    <!-- MAIN --> <vbox><import resource="assets/ui/common/nested.xml" /></vbox>
    Copy code
    <!-- NESTED --> <label>Foo</label><label>Bar (not parsed)</label>
    I would like to do
    Copy code
    <!-- NESTED --> <neutral><label>Foo</label><label>Bar (happily parsed)</label></neutral>
    Then
    Copy code
    <!-- MAIN --> <vbox><import resource="assets/ui/common/nested.xml" /></vbox>
    would be the same as
    Copy code
    <!-- MAIN --> <vbox><label>Foo</label><label>Bar</label></vbox>
    . Does it make sense or is there another workaround ?
  • b
    hmmm, no, but i do get your meaning / usecase... i wonder if something like an "omit parent" property would work
  • b
    or omitRoot, or something
  • b
    and actually, looking at the haxeui xml parser it should be silly easy to implement
  • b
    everything gets turned into intermediate "ComponentInfo" classes... the import just builds another of these and add its to the parent... no reason why it couldnt do the same but only for the child nodes
  • b
    that was easy 🙂
  • b
    main-view.xml:
  • b
    Copy code
    xml
<vbox style="padding: 5px;">
    <hbox style="padding:5px;background-color: blue;">
        <vbox style="padding:5px;background-color: yellow;">
            <import source="nested.xml" />
        </vbox>
        <vbox style="padding:5px;background-color: yellow;">
            <import source="nested.xml" omitRoot="true" />
        </vbox>
    </hbox>    
</vbox>
  • b
    nested.xml:
  • b
    Copy code
    xml
<vbox style="padding:5px;background-color: red;">
    <button text="Button" />
    <button text="Button" />
    <button text="Button" />
</vbox>
  • b
    done and in haxeui-core git 🙂
  • b
    ^^ @User
  • c
    Hohoho omitRoot="true"
  • c
    Pull and tested ok ! You are the man Ian !
  • b
    🙂 its a good addition to be honest, there are a few times when i didnt actually want the root, but thought - meh, its fine, ill deal with the additional component - but having the omit property would have been more useful / correct
  • b
    thankfully the way haxeui parses the xml makes things like this no brainers
  • c
    Nice, it makes a huge difference specially with avoiding reading lengthy XMLs and copy pasting and breaking.
1...560561562...1687Latest