https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    thats the general idea, but i think there are issues currently with exactly how tight / easy that integration is / will be...
  • l
    @bitter-family-72722 I should've mentioned I am running Haxe 3.4.7 - I have yet to port my app over to Haxe 4
  • b
    @brave-kangaroo-30399 - range, progressbars & sliders seem to kill it too 😦
  • b
    ... and dropdowns when you click on them
  • b
    and something to do with scrollviews... 😄
  • b
    basically "the demo" wont really run without stripping out pretty much all of it
  • b
    how do you update flixel? I wonder if thats the issue?
  • b
    hmmm, already up to date
  • u
    what's the error?
  • b
    this is the flixel demo:
  • b
    as opposed to the full working (haxeui-html5):
  • b
    ill grab the error, two secs
  • u
    what's the demos name I dont see one in there called haxeui
  • b
  • u
    o ok thankss
  • b
    Copy code
    Called from haxe.ui.validation.ValidationManager::process haxe/ui/validation/ValidationManager.hx line 125
Called from haxe.ui.core.ComponentValidation::validateComponent haxe/ui/core/ComponentValidation.hx line 170
Called from haxe.ui.core.ComponentValidation::validateComponentInternal haxe/ui/core/ComponentValidation.hx line 224
Called from haxe.ui.core.Component::validateComponentStyle haxe/ui/core/Component.hx line 1271
Called from haxe.ui.core.Component::applyStyle haxe/ui/core/Component.hx line 1321
Called from haxe.ui.backend.ComponentImpl::applyStyle haxe/ui/backend/ComponentImpl.hx line 156
Called from haxe.ui.backend.flixel.FlxStyleHelper::applyStyle haxe/ui/backend/flixel/FlxStyleHelper.hx line 91
Called from flixel.util.FlxSpriteUtil::drawRoundRect flixel/util/FlxSpriteUtil.hx line 350
Called from flixel.util.FlxSpriteUtil::updateSpriteGraphic flixel/util/FlxSpriteUtil.hx line 545
Called from openfl.display.BitmapData::draw openfl/display/BitmapData.hx line 977
Called from openfl.display.BitmapData::__drawCairo openfl/display/BitmapData.hx line 3041
Called from openfl.display.CairoRenderer::__render openfl/display/CairoRenderer.hx line 171
Called from openfl.display.DisplayObjectContainer::__renderCairo openfl/display/DisplayObjectContainer.hx line 911
Called from openfl.display.DisplayObject::__renderCairo openfl/display/DisplayObject.hx line 1700
Called from openfl._internal.renderer.cairo.CairoDisplayObject::render openfl/_internal/renderer/cairo/CairoDisplayObject.hx line 49
Called from openfl._internal.renderer.cairo.CairoShape::render openfl/_internal/renderer/cairo/CairoShape.hx line 148
Done(1)
  • b
    ok, i commented out the 
    FlxSpriteUtil.drawRoundRect
    lines
  • b
    will try adding bits back in now
  • b
    ok, thats better
  • b
    FlxSpriteUtil.drawRoundRect(sprite, rc.left, rc.top, rc.width, rc.height, radius, radius, color, lineStyle);
    kills something
  • b
    ok, @fierce-restaurant-45913 - i think (think) i can see what some of the issues are here...
  • b
    it seems you are using 100% widths alot, but never setting the parents either a fixed width, or a percent width... example:
  • b
    Copy code
    xml
<vbox>
    <button width="100%"/>
</vbox>
  • b
    100% of what?
  • b
    if the vbox was "width=300" or "width=100%" then it would work (again, assuming the parents vbox could be calc'd), im not 100% sure this is the issues, but just testing it now
  • b
    ok, nope, thats an issue, but not the issue... For some reason using the css 'width:100%' on a textarea (instead of 'percentWidth=100') causes:
  • b
    yup, minimal test case:
  • b
    Copy code
    xml
<vbox width="100%" height="100%" style="padding: 10px;">
    <style>
    #test {
        width: 100%;
    }
    </style>
    
    <textarea id="test" />
</vbox>
  • b
    😮
  • f
    in the sample i've send you it's even more strange the the 2nd and the 3rd tab have textarea with the css width: 100%; but are loaded in a foreach loop and don't cause crash
1...656667...1687Latest