Haxe

That's it. That's me being productive for tonight.

...
I lied. Button problems now has an issue with some examples in it. Screenshots at the bottom of the error report. <https://github.com/haxeui/haxeui-flixel/issues/20>

hmmm, yeah, that all looks a little broken, this used to be fine, correct?

hxcpp looks fine... im a little behind with flixel, openfl i think... so something may have changed... trying html

html also fine... so i guess something is different in either flixel or openfl... what versions are you running?

```
lime: 7.2.1 7.3.0 7.5.0 7.6.1 7.6.2 [7.6.3]
openfl: 6.2.0 8.0.0 8.1.0 8.8.0 8.9.0 8.9.1 8.9.2 8.9.3 8.9.4 8.9.5 [git]
flixel: 4.6.0 [4.6.1]
haxeui-core: 0.0.4 1.0.4 1.0.6 [dev:C:\Work\HaxeUI\haxeui-core]
haxeui-flixel: [dev:C:\Work\HaxeUI\backends\haxeui-flixel]
```

is there no haxelib release for haxeui-flixel?

<@83211208903098368> - quick question regarding completion breaking for createInstance: is there a way to tell the completion server "here is a file"... i mean, i may be barking up the wrong tree, but could it be that it doesnt have "assets/main.xml" ?

not sure what you mean by "have", it's not like there's a virtual filesystem or something?

OK, so if i have a macro that reads a file that is local to the project

how does the server know where that file is?

not sure what that has to do with the server, it works just like in a regular compilation

right, so its just doing a normal compile in the working directory of the project?

except that it reuses some things if possible on subsequent compilations

right, so its unlikely that it is about not finding "assets/main.xml" then?

I don't see why that would be an issue only the second time around

for me its the first time round... well, anytime round

if i try and compile that project from the issue, i always get:

```
C:\Users\ianha\Downloads\_master>haxe --connect 6000 html5.hxml
Type not found : assets.Main
src/Main.hx:8: lines 8-22 : Defined in this class
```

its never successfully compiled in vscode either for me

well, vscode is a slightly different matter

"building cache" that happens on startup is already the first build

right, well, command line has never built for me either

sounds like the guy in the issue couldn't reproduce this on the command line actually

have you tried simply printing what the working directory is when you try to read that file?