https://linen.dev logo
Powered by
# haxe-ui
  • b
    so pretty much it makes a component use the haxeui default, even when something else is accessible?
  • b
    yeah, i mean, its defo "good practice" to use the things that haxeui supplies, but for composite only, you really dont need to care that much
  • b
    with a higher priority
  • b
    essentially, yeah, pretty much all backends are composites, which means they will, for example, create an instance of the builder that will build the component
  • b
    haxeui-hxwidgets for example will ignore that, and either supply its own custom one (which is an option) or use a default one (which is more common)
  • b
    so a composite in hxWidgets backend wont use the OS default, right?
  • b
    it will but it will look super shitty
  • b
    a recent example is the calendarview, which wasnt setup to have a proper native counterpart, so instead haxeui tried to construct one out of native buttons etc (ie, a native composite)
  • b
    i think u should add the color thing as a haxeui component and push 1.4.1
  • b
    there were so many little, but necessary fixes: wxWidgets update openfl arrows Menus ...
  • b
    naw, it needs more testing, and ill probably bump directly to 1.5
  • b
    push it to git, ill battle test it for sure
  • b
    i need to integrate it into the app im working on first, which im not going to do yet as ive spent all morning on this and really shouldnt have 😄
  • b
    i think a lot of the changes u make in haxeui should just be pushed and battle tested, because the community using haxeui is active here and can communicate with you about the features
  • b
    so if you push git and someone encounters a bug, he can easily just report it and someone can push a fix
  • b
    btw, by "draw" do you mean a sidebar? or accordion? Both are available in haxeui fyi - check out the explorer
  • b
    sure, but i also dont want to get totally overwhelmed with issues for a component that i already know has some issues - its a quick way to get burnt out working on haxeui (been there before)
  • b
    i usually let new components incubate for a little in some type of "real" use, then once i think they are "alright" ill release them into the wild - usually as part of an official update so issues all flow in at once
  • b
    ... ... ... otherwise, im constantly chasing fixing bugs for other people when i need to working on other things (ie, paying "work work")
  • b
    true tbh
  • r
    This is the same crash I was getting on brave in the builder that I couldn't repro for you
  • b
    weird
  • a
    There's generally a "minimal" amount of testing one should do to make life easier on both the users and the dev
  • a
    ohhh i was looking for a side bar
  • a
    conventionally it's called drawer, so never clicked that particular option
  • b
    (so i can get the CDN link 😉 )
  • o
    It is not one div per pixel that seemed to be too heavy in most cases. It seemed to cope with horizonal stripes, redrawing was also heavy but changing color seemed to work if you just kept like an array/list without making them full on divs.. ?
  • o
    nice demo
  • b
    fyi, breaking change: Ive refactored Dialogs.selectFile (and its dialog SelectFileDialog) to Dialogs.openFile (and OpenFileDialog)... this is to make things consistent for the upcoming Dialogs.saveFile (and SaveFileDialog)
  • b
    ive also made it so that you can use these specialized dialogs like other dialogs:
    Copy code
    haxe
var d = new OpenFileDialog();
d.options = ... // optional
d.onDialogClosed = function(event) {
    if (event.button == DialogButton.OK) {
        trace(d.selectedFiles.length);
        trace(d.selectedFiles[0].fullPath, d.selectedFiles[0].name);
    }
}
d.show();
1...110311041105...1687Latest