https://linen.dev logo
Powered by
# haxe-ui
  • b
    crazy
  • f
    nice
  • f
  • f
    I have a question.... been playing around with it trying to figure it out..... resizing a component by dragging a corner of it.... is that possible in HaxeUI?
  • b
    its possible if you link it up yourself, theres nothing inbuilt in haxeui though
  • f
    Alright. I had come across some css. That would be the route to go correct? using a custom component
  • b
    css wouldnt do it... or maybe im not understanding, what / how were you planning on using css?
  • f
  • b
    right, thats not a thing in haxeui css
  • f
    ah ok
  • b
    resize: both;
    isnt supported
  • p
    So I have an abstract enum that needs to be the items of a dropdown. Is there a way to run the macro on the enum in the xml Such that it is populated by the macro? Using https://code.haxe.org/category/macros/enum-abstract-values.html to get the list
  • b
    the script tags do run at compile time
  • b
    however, that script tag there isnt going to work
  • b
    i think the simple answer is no (to what you are asking), i think you'll have to do it the old fashioned way and populate a data source in code (or in a script)
  • p
    ok, thanks
  • b
    maybe something could be added to the tag, like "" but i dunno how it would work
  • n
    Seems like hxWidgets complains if you try to compile with the 
    -D analyzer-optimize
    directive
  • b
    oh yeah?
  • b
    ill check it out tomorrow
  • o
    data like json
  • o
    so the json would be defined for the component
  • o
    you could then pass the correct json to populate
  • o
    is that kind of what they are talking about
  • f
    @User It took me a while, but understanding it and being able to visualize it clearly finally hit me... creating a canvas element for HaxeUI to utilize is a very simple thing to do. I hate when my mind tries to overcomplicate a process, but i generally learn a few things along the way. Btw, thank you for your patience with me over the past year or so when it seems like some things I ask about may seem like you've covered them before. Sometimes I have to look at things from different perspectives until one of them causes the "ah hah!" moment.
  • f
    I'm able to see the simplicity of creating custom components better now, and utilizing the DOM elements.
  • b
    nice one
  • b
    > I'm able to see the simplicity of creating custom components custom components / wrappers in haxeui can be alot of fun (and very useful):
  • b
    Copy code
    xml
<vbox id="graphContainer" width="800" style="spacing:20px;">
    <hbox width="100%" style="spacing:20px;">
        <bar-graph id="bar1" width="33%" height="200" />
        <bar-graph id="bar2" width="34%" height="200" sort="desc" />
        <bar-graph id="bar3" width="33%" height="200" sort="asc" />
    </hbox>
    <hbox width="100%" style="spacing:20px;">
        <bar-graph id="bar4" width="50%" height="200" />
        <bar-graph id="bar5" width="50%" height="200" sort="asc" />
    </hbox>
    <hbox width="100%" style="spacing:20px;">
        <bar-graph id="bar6" width="100%" height="200" hideXAxis="true" barSpacing="0.0" sort="desc" roundBarWidths="true" />
    </hbox>
</vbox>
  • o
    Does HaxeUI provide a container for haxe WebGL element
1...776777778...1687Latest