https://linen.dev logo
Powered by
# haxe-ui
  • r
    Ah
  • c
    i see, thank you
  • a
    i thought that backend was abandoned since the last commit was made last year
  • b
    Nope, certainly not abandoned... i had some issues with genjvm, but that was an age ago, so now its just a matter of finishing off the new backend.
  • b
    The wxwidgets guide on the haxeui site says to use 
    configure: ../configure --with-opengl --disable-shared
    when building the wxwidgets dependency from source; do I also need to specify the 
    --with-gtk3
    switch, or any other particular switches to get it to function correctly with haxe and haxeui?
  • b
    not as far as i remember... ive built it a bunch times and never remember having to specify the GTK version
  • c
    is there any plans for an 
    ios
    backend?
  • c
    Hello there.
  • c
    I have an exception using the dialogbox. "The syncValidation returned too many times during validation. This may be an infinite loop. Try to avoid doing anything that calls invalidate() during validation." thrown after the second call to myDialog.show(true);
  • c
    As I am not changing anything between the 2 calls, what could it be ?
  • c
    *I am not changing anything... not true I am updating myDialog.message
  • b
    im certainly thinking about an ios backend, bit i havent even tried to write a non-haxeui app from haxe at this point (or any language for that matter), so simply put i have no idea what it would entail... but its certainly something i would like to do
  • b
    Do you have a repro project? Easier to understand / reproduce that way
  • c
    not yet 😉 but will do
  • b
    👌 perfect, thanks 🙂
  • c
    actually in this minified the exception is thrown anyways. (not updating the .message)
  • c
    oh I see https://github.com/haxeui/haxeui-core/issues/382 but still the exceptions yields even with not setting width / height values
  • b
    OK, so the reason is that after you close the dialog, the dialog is internally destroyed
  • b
    so when you try to show it again, it screws up, ie, it doesnt have children, etc... i think the error could be a little more useful though
  • b
    in this case, since you want to resuse the dialog, set 
    dialog.destroyOnClose = false
  • c
    Now i remember reading that ... ☺️
  • c
    Thanks
  • b
    i think ill make the error more obvious, or try to
  • b
    ok, you should get a better error now: 
    There was a problem validating this component as it has already been destroyed
  • c
    Thanks !
  • b
    @User I'm curious what your take is on including the Toolbox.init() as suggested on the HaxeUI page for wxWidgets? I noticed in your demo [example](https://github.com/haxeui/component-examples/blob/master/demo/src/Main.hx) that you didn't seem to import any of the libraries I did to satisfy the boilerplate dependencies from running 
    haxeui-core create wxwidgets
    .
  • b
    > import any of the libraries I did to satisfy the boilerplate dependencies Can you expand on what you mean? Im not sure i follow
  • b
    The directions on the hxwidgets backend configuration page (http://haxeui.org/getting-started/haxeui-hxwidgets/) says to run 
    haxelib run haxeui-core create hxwidgets
    which in turn generates a boilerplate Main.hx. There are no imports mapped in the boilerplate code, the Haxe Interpreter will help debug the dependencies in the code. The same page also says to include the following code block before haxeui framework in initialized:
    Copy code
    haxe
Toolkit.init({
    frame: frame // the frame on which 'Screen' will place components
});
    What I was noticing in your demo code is that you didn't import 
    haxe.ui.Toolkit
    nor have the init code block. I want to know why, or why the directions on the site say it is necessary when it doesn't appear to be by the example code you made.
  • b
    Ah, i got you... OK, so the reason is that the code created with 
    create hxwidgets
    uses 
    HaxeUIApp
    ... this takes care of all that boiler plate for you
  • b
    including creating the top level frame and starting the event loop
1...757758759...1687Latest