@bright-gpu-74537 and @brave-kangaroo-30399 - a test case which includes only the relevant classes is now posted at https://github.com/greysondn/haxeui-tests/tree/master/02-textflownull (commit efbb5fd as of this writing)... It is not, by far, minimal. I keep trying and failing, but I will slowly cut out what I can over the coming days, bit by bit, if you want to wait for when I say "I completely give up" before starting anything. In order to get this to break, all that is necessary is - * build for flash debug * click the FAQ button on the title state * let lorem ipsum text load and then exit FAQ state * CRASH

I suspect - although I don't know yet - that I may have uncovered two errors. This is where I'm at, however.

The error on text flow is the same text output into the error box. One at a time; this one is whatever it is.... and hopefully it's the same one... if that makes sense at all, I don't know, I'm losing my mind anyway and wanted to get this much out there before I lose all of it.

Also be aware that due to the draw issues on flash the fake BG images which are loaded include initial state images of the buttons, because I got sick of hearing from downwind "where are the button backgrounds" 😉

Might save your sanity if you try removing them in the XML and go "why are they still there?"

I can also, apparently, highlight a single line that points to a short function for you. If you comment out this line, the error no longer happens. https://github.com/greysondn/haxeui-tests/blob/efbb5fdee7870c18ed33c45fb6c2b90c2e097bdc/02-textflownull/source/net/darkglass/consume/substate/FAQSubstate.hx#L45 There it is at the indicated commit.

So yeah, the current commit is somewhat simplified. I'm sure a more minimal case exists but... that's all I'm doing tonight on it, anyway. (Commit f60a7e1 )

Oh well if it crashes on flash that doesn’t sound like it’s my fault 😛

It would be in poor taste to convince an educator that anything is a lost cause.

Nor would it be in good sense to assume that just because it definitely happens in Flash it doesn't happen anywhere else.

I meant as far as OpenFL’s TextField, which doesn’t exist on Flash

You know what? I have reached this point where I think maybe you should rethink the implementation anyway, but that's beyond the point.

Dismissing my input simply because I'm stuck in flash is quite unhelpful. Refusing to even examine it seriously is equally so.

I just woke up, I was going to look at it later

Since it might be in a backend

Then perhaps if you don't wish for this to become the dialogue it needs to be more clear that you're joking and not trying to be antagonistic.

I think my code is garbage. "Oh well." So does every programmer I've ever talked to that was worth anything. I'm sorry if the test case actually is garbage.

But what has arisen is an error with no way for me to trace the actual root source of it. That's not a joke. That's a serious problem, of and in itself.

Before we even talk about whether the problem is in flash or the backend.

These things, you know. I could rant for hours, but as a rule, I try not to waste too much time while I'm vomiting my brains over the interwebs.

I figure, if nothing else, saying "uh, this might be broken" has to be of some value.

And then this is what I get. Christ.

I want to be clear that while I'm frustrated I don't necessarily see you as owing me anything. I don't mean "Rah, you must do this because I say so" by the above. It's handed to you because I can't figure it out where I'm at and you're upstream. The frustration is with how it seems to get me treated, not with whether or not you end up doing anything about it.

I dont think the above "not my problem" joke was meant with malice, more humour (at least thats how i took it)... I realise bugs can be frustrating, no doubt, but also time is very much at a premium (for all those involved i would guess)... that all said, minimal examples certainly help, which you have provided - so that gets the ball rolling. It might also make sense to open an actual issue on haxeui-flixel (or core if you think its an issue with core). It usually going to be better to have discussions about issues on issues rather than on chats (i think, personally anyway) Suffice to say that i think MSGHero will take a look at your issue when he can (if he can) and im happy to take a peek at it too (more eyes never hurt) but sometimes things are just slower than we would like 😃

If I were MSGhero I will simply discard this issue completely, forever. Just because of the rant.

i think dismissing an issue because of how its phrased isnt a great philosophy (personally)... if someone found a bug in something and opened and issue "this is broken, fix it now!" then, regardless, i think the issue should be looked into as its still a bug, and could have other implications. That said, i know that when i open issues / discussions on OSS projects i come from the point of view that its likely that person has a very finite amount of time and patience for me.

Well not forever perhaps. Just until someone else (or the original author) raises the same issue with some proper attitude.

People just need a lesson sometimes.

and my philosophy is that ranting won't speed up the fix, but slow down.

You know, I really don't sleep.