https://linen.dev logo
Powered by
# haxe-ui
  • b
    yeah, everything certainly looks more right... hard to see fully, but certainly looks more correct than the last time i saw it
  • b
    i wonder why you have spacing between your buttons in button bar though
  • b
    are you using Std.int(width) in handleSize? If so, is it better without it?
  • a
    i do
  • a
    here's what it looks like without it
  • a
    wrong buttons 😂
  • b
    looks more correct to me
  • a
    but now things have the subpixel artifacting 🤔
  • b
    yeah, this can be a pain
  • b
    you might need to int x/y too... ill check it out a little later, but i think heaps had a similar issue
  • b
    kha too mebbe
  • b
    @ambitious-knife-25690 A useful setting that can be used in ceramic meshes and quad objects is 
    roundTranslation = 1
    . With this, the renderer is rounding the final points to match the screen size
  • b
    oh, thats a nice touch
  • e
    im not sure if im just blind, but what component does a 
    vbox
    tag in xml represent?
  • a
    wdym?
  • a
    all components are built from ComponentImpl and ComponentSurface
  • a
    you don't need to worry about individual components
  • a
    it's actually super nice
  • a
    so like, once you type componentsurface, setup handleSize and handrePosition in componentImpl, you'll have the 'base' of a box
  • b
    NotBilly is right, you dont really need to care - however, to answer your question, 
    <vbox />
    is an xml alias for 
    <box direction="vertical" />
    or 
    <vertical-box />
    ... so the actual class is "VerticalBox"
  • b
    same goes for sliders, scrollbars, progressbars... you can do 
    <vslider />
    , 
    <slider direction="..." />
    or 
    <vertical-slider />
  • b
    if an 
    IDirectionalComponent
    doesnt have its 
    direction
    set, 
    horizontal
    is assumed
  • b
    so 
    <slider />
    is 
    <slider direction="horizontal" />
    and the class is 
    HorizontalSlider.hx
  • e
    but for a native backend, it has to become some native ui element. i cant seem to find where haxeui-hxwidgets would handle creating a "VerticalBox" or "HorizontalBox"
  • b
    well, these components dont need native counter parts since they are just containers
  • b
    so in wxwidgets its just a base "wxPanel"
  • b
    so native or not, you'll still want / need some composite features
  • b
    thats why i personally think it makes sense to create a composite backend then map native components
  • e
    well the way i see is that if i make a composite backend ill get all the composite components "for free", but ill have to get input working myself, or if i make a native backend, i have to map all the components to godot ones, but ill get input handling and mouse events "for free"
  • e
    also a backend can add new components too right? so like afaik haxeui doesnt have a video player element, but godot does, so i could add that to the backend
1...140714081409...1687Latest