https://linen.dev logo
Powered by
# haxe-ui
  • b
    well, but its not just 0 though
  • b
    Copy code
    xml
<box width="50">
    <button width="100" />
</box>
  • b
    for now btw i have fixed the original issue with findComponentsUnderPoint
  • b
    (and therefore the placeholder issue)
  • c
    Rock star !
  • b
    fyi, you might want to pull latest haxeui-html5 also, found a tiny bug where measuring text size would be a little off
  • c
    haxe/ui/layouts/DefaultLayout.hx:74: WARNING: trying to use a % height in a child (id: stepper-step) with autosized parent (id: MyNumStepper) Log.hx:66:3 haxe/ui/layouts/DefaultLayout.hx:61: WARNING: trying to use a % width in a child (id: null) with autosized parent (id: MyDDCalendar)
  • c
    I got these with default NumStepper and DropDown calendar
  • b
    hmmm
  • b
    hmmm, yeah, so actually those layouts do make sense
  • b
    they have another component that makes the autosize size the component, then another 100% that takes up that size
  • b
    something like:
  • b
    Copy code
    xml
<hbox>
    <button height="50" />
    <button height="100%" />
</hbox>
  • b
    i actually dont get the warning though
  • b
    sorry, yes i do
  • c
    Though useful, The warning could be confusing for those that start using those comps
  • b
    yeah, ill either see if i can fix it, or drop it... for now i think im just going to comment them out
  • b
    i do like them, but its giving false positives
  • c
    yep
  • b
    ok, they are gone until i have more time to make them more "correct"
  • a
    hello, how does one jump from one part of the document(?) to another on button press, similar to html's href="#element-id"?
  • b
    im not sure i follow... what "document" ?
  • o
    I guess he wants the page to scroll to the area that's linked or highlight a linked area when a button calls it.
  • a
    yes, basically that
  • a
    i said document because i dont know what the correct term for the whole page would be for haxeui
  • p
    yes, I ended up with
  • p
    then Toolkit.theme = "joedark";
  • b
    there was an 
    ensureVisible(someComponent)
    in ScrollView... but it has some issues... need to look at that actually as ill need / want it soon for the upcoming "actions"
  • b
    OK, so thinking about it, you should be able to just do:
    Copy code
    xml
<themes>
        <default>
            <style resource="hosey/light.css" />
        </default>
        <dark>
            <style resource="hosey/dark.css" />
        </dark>
 </themes>
    are you saying that didnt work?
  • a
    what exactly are those issues? it doesnt work in some of the backends?
1...755756757...1687Latest