https://linen.dev logo
Powered by
# haxe-ui
  • m
    yes
  • b
    as for the dragging stuff, yeah a test project would be useful
  • m
    I have that just in hand, give me 2 min
  • b
    for scale, yeah, haxeui isnt going to touch the scale of other parts of an openfl app, just "itself"
  • b
    no rush, heading off now anyway
  • m
    Ok, I'll leave it here
  • m
    Btw one more thing this:
    Copy code
    xml
<label text="${frameRateSlider.pos}" />
    Is failing with:
    Copy code
    haxeui-core/git/haxe/ui/macros/ComponentMacros.hx:811: characters 23-51 : Float should be String
haxeui-core/git/haxe/ui/macros/ComponentMacros.hx:811: characters 23-51 : For function argument 'listener'
src/Main.hx:11: characters 34-83 : Called from macro here
    frameRateSlider is a slider component.. This code use to work a while ago
  • b
    it used to use hscript so it probably got away with it, now its using real haxe code, which is less forgiving i guess the result of that should be automatically wrapped in an Std.string
  • m
    No worries, I can workaround by code anyway
  • m
    Copy code
    css
.debug_displayList {
    background-opacity: 0;
}

.debug_displayList > * {
    background-opacity: 0;
}
    I tried this, doesn't work.. Not on openfl at least... Still displays a white background
  • m
    Nevermind, I'm too dumb, I mean forget the css question
  • m
    I obviously forgot to process the css
  • m
  • m
    To reproduce just click Widgets > Performance, drag the widget by the top bar
  • m
    Note that I wrote:
    Copy code
    haxe
Toolkit.scale = 1.2;
Toolkit.init();

scaleX = 1.2;
scaleY = 1.2;
    If I remove the last 2 lines, dragging works fine, but something that is width=100% in xml won't fit the screen width for example.
  • m
    Wrapping in Std.string worked 🙂
  • b
    would be better for haxeui to do it though
  • b
    OK, there are some fixes in haxeui-core and haxeui-openfl: * you shouldnt need to set the 1.2 scale on the openfl sprite, this was actually a bug in haxeui-openfl since you were using addChild rather than addComponent - which is fine, but it screwed with the scale, you can if you want (or set it to a different value) but the act of setting it was working around a bug where the root component wasnt having its scale set correctly since you "bypassed" addcomponent - which again, should have been totally fine - and is now * dragging works properly, regardless of scale or where you add the component (which is what was causing the bug) small note: you dont need to set "autoScale = false", the act of setting the scale manually turns off auto scaling - just an fyi
  • b
    OK, also in latest haxeui-core you shouldnt need to so this, haxeui will try to convert between simple types (string, float, int, bool)
  • b
    Copy code
    xml
<slider id="theSlider" pos="50" precision="0" />
<label text="${theSlider.pos + 100 + ' items'}" />
<label text="${theSlider.pos}" />
<slider pos="${theSlider.pos + 10}" />
<textfield id="theTextField" />
<checkbox selected="${theTextField.text}" />
<slider id="theOtherSlider" min="0" max="1" step="1" />
<checkbox selected="${theOtherSlider.pos}" />

<hbox>
    <listview id="lv1" width="100" height="100" selectedIndex="${vslider.pos}">
        <data>
            <item text="Item 1" />
            <item text="Item 2" />
            <item text="Item 3" />
            <item text="Item 4" />
            <item text="Item 5" />
            <item text="Item 6" />
            <item text="Item 7" />
            <item text="Item 8" />
            <item text="Item 9" />
        </data>
    </listview>
    <slider id="vslider" height="100%" direction="vertical" max="${lv1.dataSource.size - 1}" step="1" />
</hbox>
  • b
    @magnificent-crayon-8615 - ive removed the previous custom alphanum sort, i really have NO idea why it was there now... dunno if something changed in haxe or... ... ... i really dont know - the in built sorts works equally well on js and cpp, so there is simply no reason for the "custom" one to be there (plus it wasnt working correctly!)... inbuilt will almost certainly be faster too... id still love to know what the rationale was for adding the custom alphanum sort in the first place
  • b
    (as a bonus, tableview nows honours the sorting if it was set before the table had data - which was a bug i noticed)
  • b
    Copy code
    xml
<tableview width="500" height="200">
    <header width="100%">
        <column id="colA" text="Column A" />
        <column id="colB" text="Column B" width="200" />
        <column id="colC" text="Column C" width="100%" sortable="true" sortDirection="asc" />
    </header>
    <data>
        <item colA="Item 3A" colB="Item 3B" colC="Item 3C" /> 
        <item colA="Item 1A" colB="Item 1B" colC="111 Item 1C" /> 
        <item colA="Item 2A" colB="Item 2B" colC="1 Item 2C" /> 
        <item colA="Item 4A" colB="Item 4B" colC="Item 4C" /> 
        <item colA="Item 5A" colB="Item 5B" colC="88 Item 5C" /> 
        <item colA="Item 6A" colB="Item 6B" colC="Item 111 6C" /> 
        <item colA="Item 6A" colB="Item 6B" colC="Item 222 6C" /> 
        <item colA="Item 6A" colB="Item 6B" colC="Item 002 6C" /> 
        <item colA="Item 6A" colB="Item 6B" colC="Item 02 6C" /> 
        <item colA="Item 7A" colB="Item 7B" colC="Item 7C" /> 
        <item colA="Item 8A" colB="Item 8B" colC="Item 8C" /> 
        <item colA="Item 9A" colB="Item 9B" colC="Item 9C" /> 
        <item colA="Item 9A" colB="Item 9B" colC="0" /> 
        <item colA="Item 9A" colB="Item 9B" colC="222" /> 
        <item colA="Item 9A" colB="Item 9B" colC="02" /> 
        <item colA="Item 9A" colB="Item 9B" colC="00002" /> 
    </data>
</tableview>
  • m
    I've tested it and it's working fine. Just have to remember to set the scale before adding the components, otherwise they won't get updated.
  • b
    yeah, its a "before init" type of thing... tbf, i think that could change really, but anyway, its low priority
  • b
    howcome you arent using auto scaling?
  • m
    How does autoScaling works?
  • b
    it looks at the device dpi, then attempts to set an appropriate scale based on that
  • m
    But won't that clash with me setting the scale directly?
  • b
    well, you dont set the scale, thats my point
1...106510661067...1687Latest