Haxe

why does hovering over it increase memory so much

looks like a leak... does it just go up forever??

seems not, but it seems to not "discard" it when changing tabs in the tab thingie

so using the app by switching the tabs can cause it to acccumulate

right, iirc it doesnt destroy each tab each time

but its a valid point, maybe there should be an option

it does mean you'd lose anything in the tabs though, so you'd have to repopulate it yourself, ie, if you typed some text in the last tab, then changed tab and back then it would destroy the whole tab and recreate it

the most i was able to get my app up to was 45 mb

yeah, that'd be useful, would be interesting to see what it peaks at when there are no text inputs

<@!385014891750096896> out of curiosity, are the `fromFile` and `fromString` functions from the `ComponentBuilder` macro class in a working state? I've tried to use them, but they don't return `Array<Field>` and I was wondering if there's any example online 🙂

Yep, just set up a simple openfl app and the behavior is the same, so I guess it's an openFL issue.

fromFile and fromString a expression macros, they will build component code "in place" and return it as an expression (which will be a component derived class)

if you want to build a class from an xml file, you can use `@:build(ComponentBuilder.build(....))`

right, i guess you should open an issue on the openfl GH, generally they seem fairly good an closing text issues - at least thats been my experience as of late 🙂

<@456226577798135808> 
```
/Users/runner/work/hxWidgets/hxWidgets/src/wx/widgets/MenuItem.hx:15: characters 189-200 : Parameter default value should be constant
/Users/runner/work/hxWidgets/hxWidgets/src/wx/widgets/MenuItem.hx:14: characters 173-184 : Parameter default value should be constant
Error: Process completed with exit code 1.
```

its on the GH actions - i dont want to enforce haxe versions unless absolutely required

Er I can't downgrade below 4.2.0 because of coconut

ill take a look, seems like it doesnt like "text:WxString = null, helpString:WxString = null"

This didn't change, isn't it most likely about ItemKind?

oh, haha, i havent pulled your PR locally 😄