Oh I thought we got rid of asComponent

It might just be null

Does that mean I can just remove asComponent or what?

Or am I just behind or...?

I've almost got that minimal case together if you wanted to check it instead of waiting for me to get my brains together. Got distracted with a KH stream from the guy who originally created the project I'm working on.

It makes no sense, becasue it happens during the text reflow, but if I just load text in, it's fine.

Other than the fact that it's quite slow.

Hold on, let me poke this a bit.

Idk maybe, pretty sure it’s not necessary

Oh I wanted to get rid of it but haven’t yet

Okay. Can I just gank it out of that function then without breaking anything?

I’m pretty sure Ian’s recent changes made it so you could

this.

all those properties instead of having to go through the cast

The puzzle I've got is why it works for the minimal case and not for the code I've got, even if I swap the classes out.

I think the issue may be elsewhere, but I'm still investigating.

On a personal note, This is really my issue with relying on macros/etc; traditionally, it's not unheard of for such things to obstruct the source of errors.

I'm growing a conviction the bug may not necessarily be in haxeui, however, so that much is good.

I should be more clear; the only noteworthy distinction which I have not, as of yet, eliminated, is the class inheritance structure being different between the two. In the case I tried to put together for you to examine, it's one specific class at one specific point; in my actual code, it's a different class at that same point.

I'm talking around it a bit because it may imply something kinda "yeowch" until I at least have some proof I'm on the right track, but it takes time to rewrite code to test that in the actual use case itself (as opposed to building a carefully crafted example that may miss other factors I'm not aware of).

Still haven't figured it out. But the good news (?) is that that specific theory was wrong.

yeah, i think think asComponent is needed anymore in haxeui-flixel, it was put there to get away from having to upcast "this" to a "Component" to get info from it, but it shouldnt be needed anymore

that said though, it should still work (unless haxeui-flixel has been changed), its just not needed anymore

a minimal sample of what you mean would probably be more useful that trying to describe an error 😃

That's the problem - I can't reproduce. It's still on my list.

btw, @loud-salesclerk-7438 - the way you use tableview is a little strange, not wrong, just a little strange...

im moving it to new-comp at the moment, well, rewriting it mostly, ill redo your sample when thats done of how i would do things

Quick heads up while my brain's in one piece - my medication and my painkillers don't mix, so I had to stop taking it, which is fine - I can deal in a quiet environment - but there's about to be a huge civil war festival basically right outside my window (I live on my town's square) for about 3-4 days. They woke me up this morning pounding tent stakes in, and it only gets worse. TL;DR : This might take a week.

rightyo - as and when 😃

well, my sample is a stripped down version from a project, that was using v1 and got converted to v2, so maybe that's where my strange way originates from or maybe I just misunderstood how things are supposed to work and settled with what worked... I remember having an issue with images not appearing in cells, or having incorrect scaling I can't wait to see your version of it it's good news that TableView will make it into new-comp, otherwise I would be stuck with whatever was latest master before your imminent new-comp merge

actually @loud-salesclerk-7438 - i take that back... i misread the code :D I thought you were using item renderers to add items to you table (just because i saw them in a loop) - but actually it was the column rendererers

😄