https://linen.dev logo
Powered by
# haxe-ui
  • b
    I think this is fixed now in latest haxeui-flixel, can you give it a whirl when you get 5 mins and see if thats the case (im assuming ive understood the problem correctly - i didnt know about the 
    StageSizeScaleMode
    stuff, thought the zoom thing was the only thing 🙂 )
  • b
    (if that isnt the issue / doesnt fix it, can i get a repro?)
  • s
  • b
    it'll need to be in a function of some kind
  • b
    the constructor is a good place... i just pasted the relevant parts, but the actual code was inside the 
    new
    function in my test app
  • h
    Thanx - should I just refresh to the latest git haxeui-core ? I assume it's core.
  • b
    yeah, just pull git haxeui-core
  • h
    doing it now ....
  • h
    will that get me the new file save dialogs ?
  • h
    I think will won't it ?
  • b
    yessir
  • b
    you'll also need to pull your backend too
  • h
    cool - I will need that shortly
  • h
    oh ok
  • h
    will do
  • h
    still having issue in vscode but it's working from powershell - vscode caching kills me sometimes
  • b
    Copy code
    I was having a lot of macro-related compiler errors in haxeui... but I "fixed" it by just disabling the compilation server in VScode
I know it's been brought up before, and it doesn't seem like an easy thing to fix. But man I could not compile twice in a row without an error
In my settings.json, I put "haxe.enableCompilationServer": false and that's it. Hope that helps someone else
Your compiles will be a second slower but you won't waste 30 seconds crashing and restarting the compilation server anyway
And you keep macro'd code completion, since that's a separate thing
  • b
    i dunno if that will help
  • h
    ok - restarting vscode did it
  • h
    thanx for the quick fix
  • b
    np - 'twas a good find, kinda surprised it hasnt come up before, i can only assume that no-one, including me, has tried to put a number in a field that was text in xml
  • b
    basically haxeui was going "ah, 123 is number, lets turn that into an actual number"... and then later trying to assign that to a string field
  • h
    nothing like users for finding missed test cases - happy to help
  • b
    it wasnt just placeholder that was affected, 
    text="123"
    would have also caused the problem
  • h
    oh ... interesting - I haven't had that requirement - so didn't see it
  • b
    yeah, any text property would have broken if you used a number in it (in xml only ofc since its all 'text')... which is why im surprised it hasnt come up before
  • b
    > I also saw some tiny bugs in the searchable dropdown, if you type something, you cannot, select the items with the keyboard anymore. And If you type the whole word "Java" for example in the component explorer, and type Enter, it doesn't select it This should be fixed now, i forward on a subset of the actions to the dropdown handler
  • b
    for the second part (ie, enter on search text field), i think im just going to expose the search text field, so you can do 
    dropdown.searchField.registerEvent(...)
    ... i think this makes more sense rather than trying to guess what people would want to do with the search field
  • b
    OK, so the search field is exposed now (
    DropDown.searchField
    ) - note, you dont have to actually open the dropdown to be able to get (or replace) the text field (usually the dropdown handler is only created once you open the dropdown), the dropdown will be smart enough to just create the search field on demand - or use the one you provide if you want (
    myDropdown.searchField = myTextField
    )
  • b
    Copy code
    haxe
myDropDown.searchField.styleString = "background-color: #CCFFCC";
1...114011411142...1687Latest