https://linen.dev logo
Powered by
# haxe-ui
  • m
    It's small enough to be understood quickly and uses both flixel and haxeui with flixel backend. And as Ian said, if you have any questions, ask away.
  • b
    > I admit when I added a label inside a progress component and it worked I felt a mix of surprise and satisfaction hahhaha Heh heh, yeah, ive done it with buttons before, but never thought about progress bars
  • h
    @User wow! I've been searching for some time for something developed in haxeflixel+haxeui to check out, very nice
  • b
    Copy code
    source/flixel/AnimationEditorState.hx:15: characters 1-48 : Type not found : guifes.extension.FlxAtlasFramesExtension
source/ui/AnimationEditorUI.hx:33: characters 12-25 : Unmatched patterns: _
source/Main.hx:25: characters 51-71 : Unknown identifier : AnimationEditorState
source/Main.hx:25: characters 51-71 : For optional function argument 'InitialState'
source/AnimationEditor.hx:25: characters 14-22 : flixel.AnimationEditorState has no field delegate
source/Main.hx:31: characters 32-52 : Type not found : AnimationEditorState
source/AnimationEditor.hx:39: characters 9-30 : flixel.AnimationEditorState has no field loadTexturePackerFile
source/AnimationEditor.hx:51: characters 14-35 : flixel.AnimationEditorState has no field loadTexturePackerFile
source/AnimationEditor.hx:78: characters 19-40 : flixel.AnimationEditorState has no field loadTexturePackerFile
source/AnimationEditor.hx:103: characters 14-36 : flixel.AnimationEditorState has no field updateDisplayAnimation
source/AnimationEditor.hx:144: characters 14-36 : flixel.AnimationEditorState has no field updateDisplayAnimation
source/AnimationEditor.hx:152: characters 14-36 : flixel.AnimationEditorState has no field updateDisplayAnimation
source/AnimationEditor.hx:160: characters 14-36 : flixel.AnimationEditorState has no field updateDisplayAnimation
source/AnimationEditor.hx:168: characters 14-36 : flixel.AnimationEditorState has no field updateDisplayAnimation
source/AnimationEditor.hx:192: characters 14-36 : flixel.AnimationEditorState has no field updateDisplayAnimation
  • b
    @User - werent you developing something in haxeui-flixel? I might be misremembering
  • h
    I am! However I don't think my project flexes haxeui's muscles, and I had some minor hiccups when implementing stuff for the first time
  • h
    so having a bigger project to look at is extremely nice
  • m
    @User and @User if you intend on building the project, remember to install this dependency as well: https://github.com/guifes/haxe-utils
  • m
    And also build the flixel ui branch!
  • m
    @User UI improving each day, thanks to haxeui
  • m
    Much to improve visually yet obviously, but it's working awesomely well
  • b
    @User 👀 ... not that I would expect you to change what you're doing at this point
  • b
    @User - cool stuff
  • b
  • b
    not sure what happened but i re uploaded it and it and downloaded it again to make sure it works.
  • m
    @User I think I need a little help understanding the inner components and their id/styleNames of the Progress component to be able to set the style correctly
  • m
    I remember you mentioned that the haxeui site only has that info documented for Button component, could you share some light?
  • b
  • b
    that help?
  • m
    that's perfect
  • b
    👍
  • m
    What value should I set "set_vscrollPos(HERE)" to make sure the scroll is always at the bottom regardless of the content?
  • m
    I thought 100 would do the work (assuming it was a float percentage) but it wasn't.
  • f
    😎
  • b
    is there any way to get rid of the flixel logo when the game starts and how can i change my icon on the exe?
  • b
    @User - noice @User - 
    myScrollView.vscrollPos = myScrollView.vscrollMax
    @User - https://api.haxeflixel.com/flixel/FlxGame.html (constructor args)
  • r
    Hi. I'm playing around with haxeui (with openfl backend) and so far, it 's really (really) great. Unfortunately, I miss a lot of things in the documentation/API/explorer/guide.. (Espacially regarding styling/theming/binding since the haxeui-guide is kind of empty ). for example: -how to properly remove the up and down buttons of a Scroll Component...? -Is there a list of the supported style properties for text ? -When extending an ItemRenderer, is there a way to "catch" some sort of "render" event to add some logic and have more control on how the item is rendering ( say i want to choose if yes or no i want the display an icon, or target another property as the default one of a component..) -What means "clonable,behaviour and bindable" and how to use them ? thanks !
  • b
    Hi! Yeah, the documentation is pretty slim :( I think ive said about 100 times that i want to improve it, but i just never get time (motivation is probably more honest) and end up just working on the actual framework. So for components children usually you can look in the styles and it will give you a fairly good indication of what children a component contains, for example: https://github.com/haxeui/haxeui-core/blob/master/haxe/ui/_module/styles/default/scrollbars.css So we can see from there there are 3 buttons that are in a scrollbar: inc, deinc, thumb. So you could do:
    Copy code
    css
.scroll .inc, .scroll .deinc {
    hidden: true;
}
    note that "hidden" isnt actually a css3 property but is specific to haxeui, i keep meaning to also add "display: none" but i havent gotten around to it yet for text (labels) i think you have: font-size, font-name, font-bold, font-italic, font-underline and color - again, alot of these arent css3 properties and i should really add the css3 version too for clarity For the itemrenderer i guess you have a few options... there is and itemRendererFn which means you can return the correct item renderer based on your data, however, this was added A LONG time ago and so it very well may not work as intended, ill have to give it another run over at some point. Another options would be to subclass item renderer (MyItemRenderer extends ItemRenderer) and then have logic in there, maybe on the override the 
    validateComponentData
    call (make sure you call the super though!). Ill have a think though how the API could be nicer here - open to suggestions ofc - and a solid test app / use case is always useful if you have one 😉
  • b
    So the metadata on fields do specific things, and for the most part you really dont need to work about anything to do with them (unless you are building your own, cross framework components - which is "all" haxeui-core is essentially), but heres a brief rundown: 
    @:clonable
    - this tells haxeui to automatically include this field when it auto builds the "cloneComponent" function... you can build your own "cloneComponent" (and haxuei macros will add to it), but this is a shortcut to not have to remember to do that
  • b
    @:bindable
    - this means that the field can be used for binding, which means you can use it xml like 
    <button text='value is ${mySlider.pos + 22} />
    , in this case 
    .pos
    of the slider would need to be annotated with 
    @:bindable
1...482483484...1687Latest