Quick question... is something like this issue reproducible on any other backends?

I havent tested others as I only use kha. But maybe @bright-yak-48460

Got back to my codebase after all this time. Updated everything too.

Getting this now

C:\HaxeToolkit\haxe\std/haxe/macro/MacroStringTools.hx:86: characters 84-89 : Cannot use abstract as value
The terminal process terminated with exit code: 1

If you happened to hit this during the advancement of haxeui or haxeui-flixel and have an inkling where it may have suddenly cropped up from, I'm interested in hearing it.

Otherwise it's apt to be forever tracking it down in this mess of a codebase. I can't even give you a minimal case out of that because I don't know why it's happened.

haxeui-flixel at git, core at git. Going to try with both of them at latest haxelib releases and see if it goes away.

Huh. Github marks 1.0 for haxelib but actual haxelib releases only showing 0.0.1

But

haxeui-flixel git master

and

haxeui-core 1.0.7

do build together. So that's good.

Either flash forgot how to put text on buttons or something changed. Do advise. That could be tested.

Oh, and my parser is fine, just wanted to make sure it's awake 😉

Can confirm similar issue in HTML5

Also note - great news! We're going to move this project over to targetting HTML5, so no more Flash headaches for any of us! Good effin riddance

Fixed. Now the text field is read properly from the XML, so the screwy way of doing before is no longer necessary.

Actually willing to do a round-up - a lot of issues with the flixel backend have in fact been fixed. I've been repairing my code to match.

That's about 6-ish months of progress we're talking.

OK, so... is there still issues? Didnt quite follow entirely...

what was the issue that was resolved (if it was indeed resolved)

Oh, I'll always find something broken. That's just me 😐

... So, previously text on buttons was

<button>text</button>

It's now

<button text="text" />

That was something I discovered last night. That was the last "fixed" there.

... Also the build state was in weird shape and the first part was just finding a combination that compiles.

That's done, too. [Edit: That was the first bit there.]

... I should have struck those as they were resolved. It would have made things a bit clearer, but my brain's going a bit faster than my hands these days. And that's why me and trainwrecks go together XD

Also noticed other things fixed in the time between. Most noteworthy given my own history is that width of elements is actually being read from the XML properly. So it's looking better. It will be some poking and prodding before I can say "good" but I'm cautiously optimistic so far.

Hello fine folks! :) Trying to compile an haxeui project gives me the following warning and error:

Warning: Ignoring requested haxelib "openfl" version "3.6.1" (version "8.9.5" was already included)
C:/HaxeToolkit/haxe/lib/lime/2,9,1/lime/graphics/cairo/Cairo.hx:34: characters 13-21 : Unexpected operator

When switching to openfl version 3.6.1, it gives me another warning and another error:

C:/HaxeToolkit/haxe/lib/openfl/3,6,1/openfl/_legacy/net/URLLoader.hx:25: characters 33-39 : Warning : This typedef is deprecated in favor of sys.thread.Thread
C:\HaxeToolkit\haxe\lib\haxeui\1,8,21/haxe/ui/toolkit/core/PopupManager.hx:15: characters 8-22 : Type not found : motion.Actuate

Did I mess something up ❓ Misc info: Windows 7 cmd is launched with admin perms Haxe 4.0.2 Dump of `haxelib list`:

actuate: [1.8.9]
box2d: [1.2.3]
haxeui: [1.8.21]
hscript: [2.3.0]
hxcpp: [4.0.64]
layout: [1.2.1]
lime-samples: [7.0.0]
lime: 2.9.1 [7.6.3]
openfl-samples: [8.7.0]
openfl: 3.6.1 [8.9.5]

"haxeui" on haxelib is deprecated

you want haxeui-core, plus the backend(s) of your choice

Downloading it right now! Thank you very much, good sir!

Project compiled succesfully!