https://linen.dev logo
Powered by
# haxe-ui
  • i
    but when I do it, I got these errors:
  • i
    for reference, here is my project.xml, I added the haxedefs, copied from the example .hxml
  • i
    I have also setup a properties file inside the source folder
  • b
    im not sure wxWidgets and openfl are going to work together at all... you might be able to embed an openfl app into a wxwidgets app
  • b
    but i feel like even then you are going to have some major headaches (as @User is well aware of)
  • i
    hmm.... should I separate the app?
  • i
    like, an entire project altogether?
  • i
    my plan is to have a crash reporting dialog (with using larsiusprime's crashdumper)
  • i
    since their tool is only just dumping, i figured i'd make a crash dialog UI
  • p
    You could just use haxeui-openfl or haxeui-flixel. (Or even raw openfl/flixel.)
  • b
    👆 I tend to agree, i think you are going to have major, major issues mixing the two, im not even convinced its possible at all tbh
  • b
    you could always have a seperate wxwidgets app that you call with the relevant info in the case of a crash, but not sure if thats overkill
  • i
    maybe i can approach it like this. since crashdumper dumps to a log folder, i could pass the arguments to the location to that dump file to an external app, and parse it
  • i
    maybe i could learn a thing or two on... something like unity crash reporter
  • b
    yup, that sounds like it would work, and a million times easier than trying to have a custom native dialog inside openfl
  • i
    yep i thought the latter would work haha thanks for the insight again
  • b
    np - good luck 🙂
  • b
    relative paths now work for sys backends with file://
  • b
    Copy code
    xml
<hbox>
    <image width="640" height="400" resource="file://C:\Temp\haxeui\issues\haxeui-core-images\build\hxwidgets\test.png" />
    <image width="640" height="400" resource="file://test.png" />
</hbox>
  • p
    PR created.
  • i
    Hello, so I tried separating the project file, i can use postbuild on the XML to build and copy the executable
  • i
    It works haha
  • s
    Having an issue with the openfl backend: I'm trying to access the openfl textfield object behind the haxeui textarea, so that I can write data to htmlText, but 
    textarea.getTextInput().textField
    doesn't write text to the textfield, and simply displays blank. I've tried using 
    textarea.getTextInput().textField.text = data;
    ,
    textarea.getTextInput().textField.htmlText = data;
    and the textfield 
    .appendText()
    function, but none of these work. Using 
    textarea.text
    does write text correctly, but the text area has no 
    htmlText
    property (unless the name for the property is different).
  • s
    Apologies if this is the wrong channel to ask, I'm not sure if this is specifically to do with the haxeui 
    textArea
    or the openfl 
    textField
    .
  • b
    nice, thanks!
  • b
    sounds haxeui related...
  • b
    does 
    @:privateAccess myTextfield.getTextInput().tf.htmlText
    work?
  • b
    OK, so htmlText is now exposed for text inputs (it was already for label). Obviously this only applies for backends that support htmlText (which i think is just haxeui-html5, haxeui-flixel, haxeui-openfl, haxeui-nme)
  • b
    Copy code
    haxe
myTextArea.text = "<font color='#ff4444'>Red</font>, <font color='#44ff44'>Green</font>, <font color='#4444ff'>Blue</font>";
myTextField.text = "<font color='#ff4444'>Red</font>, <font color='#44ff44'>Green</font>, <font color='#4444ff'>Blue</font>";
myLabel.text = "<font color='#ff4444'>Red</font>, <font color='#44ff44'>Green</font>, <font color='#4444ff'>Blue</font>";
  • b
    its worth noting that you can use 
    .text
    or 
    .htmlText
    , haxeui will attempt to guess the appropriate property based on the content (as it already does with 
    Label
    )
1...706707708...1687Latest