https://linen.dev logo
Powered by
# haxe-ui
  • b
    hmm, yeah, i dont think haxeui-heaps gets images from the res folder, i think they'll have to be haxe resources - that said, it should work with both - but i dont think the native framework part is written, ill check
  • b
    it doesnt sound like the indented way - but its hard to follow without code, maybe you can knock up an example of exactly what it is you are trying to do?
  • l
    The above example was effectively what I was trying to do
  • l
    The act of re-declaring UI elements was causing issues for me
  • l
    and I had trouble recreating the specific null access error i was getting in my project
  • b
    OK, but hideDialog is going to destroy the dialog (and its children) unless you set destroyOnClose to false
  • b
    and then you'll need to hold a ref to it, and not add your button to it over and over again
  • b
    is the idea to reuse the same dialog over and over again?
  • l
    Yeah. i figured it would be easier to just re-declare each time since it'll be frequently opened and closed
  • b
    ie, if you had, say a text box in there, you typed into that text box, when you close the dialog and open it again you'd want that newly typed text to be there? Ie, you dont want a new instance of the dialog each and every time?
  • l
    Yeah pretty much. My confusion was if it was the correct approach to it since the way I was going about it was causing odd behavior
  • l
    Since I saw that closing the dialog was destroying the dialog, I would just re-declare it each time it needed to be opened again
  • l
    It was only after I learned you could tell it to not destroy itself, so that was the 'workaround' I was talking about, which is apparently the intended method
  • b
    so i mean, the problem is you have kinda done half of both methods...
  • b
    your code is all fine, except that you create the "closeMe" button once and it adds it to the dialog on the onclick of "openMe" (which seems a little strange in the first place)
  • b
    now when that dialog is destroyed (which is the default) then that closeMe button is destroyed, never to be created again
  • l
    Okay that makes sense
  • l
    So then there was a second problem I was expecting then, with that in mind
  • b
    so then when you click the "openMe" button again, it tried to add the closeMe button again, but its not valid anymore
  • l
    I was creating the whole ui again a second time.
  • b
    so if you wanted to reuse the dialog then i would create the dialog (and the button / contents) once and just reuse that over and over again
  • l
    Let me remake that as a minimal and maybe then I'll get the error
  • b
    (but you will have to set destroyOnClose = false)
  • b
    alternatively, you can create a new instance of the dialog each time (as you are doing in the openMe click event) but you will also have to create a new instance of the closeMe button since it will be destroyed when your dialog is
  • l
    That's what I thought I was doing, but I can't reproduce
  • l
    well, darn.
  • b
    have you pulled latest haxeui-heaps?
  • l
    Not since the last fixed I requested
  • b
    OK, well, fair enough, i fixed a bug specifically around dialogs (ish), so you will 100% want to pull haxeui-heaps
  • b
    thought maybe thats why you couldnt repro
1...814815816...1687Latest