hmmm, something odd is happening... any chance you could try and whittle it down to a minimal repro?

I'll do it later today

nice one, thanks 🙂

I thank you sir!

🙂

To reproduce the issue. Navigate to the Shop tab and click randomly on the empty "item slots" on the top of the screen. @User

I think I found out at least "where" the problem is. I dug a little and found out the null pointer is now coming from FlxSpriteGroup line 293 which is:

haxe
sprite.scrollFactor.copyFrom(scrollFactor);

scrollFactor is null in this case. So looking at my code, seems like it is problematic to reuse a component after I removed it from another component. I think removeAllComponents() is disposing the flixel part of the removed components or messing with their internal state. So I changed my code to the following and everything worked fine.

haxe
private function onShopItemClicked(item: Item)
{
    switch(item.getTemplate().type)
    {
        case WEAPON:
            itemDescription.removeAllComponents();
            var weaponDescription = new WeaponDescriptionBox();
            weaponDescription.populate(item);
            itemDescription.addComponent(weaponDescription);
        default:
    }
}

Not sure if this is a bug, or I just shouldn't reuse component instances. If it's the later, at least I didn't know I shouldn't.

there is a parameter for removeComponent (dispose=true)

i guess that isnt exposed in removeAllComponenents

oh, it is

does setting that to false help?

I'll try it out!

It did not crash, but also the component did not show up after being added again

I've seen an app builder project showcased on the haxeui site, i was wondering is this a working project and is it publicly available?

Which app builder?

OK, so that sounds like a bug in haxeui-flixel... maybe its not honouring the "do not dispose" and always disposing... ill check it out

ah, that was a play around when i was messing around with adding classes to hscript... to be honest, its something id like to come back to at some point

Was it directly related to the fact that classes were added or did it just happen to be at the same time?

So it was really to test out hscript-ex in a kind of "real life" env... ie, that "haxe code" you see there isnt haxe code at all, its hscript code

ah right :o

so i'm guessing it isn't public yet?

the builder thing / "os" thing isnt, nope... i do have some ideas for a real builder (integrated into that hxIDE thing ive been working on)... but ive been so busy recently with "work work" that ive had little to no time to work on anything else

is hxIDE a separate thing?

yeah

even if the code was up somewhere without being properly finished or officially released it might help other people or inspire them to do their own things, that way even if you don't have time to work on it right now your work can still be helpful to others that is if you plan on making it open source ofc :p

yeah, ill see about putting it online 🙂

is there a straightforward way of making a

Do not show again

checkbox for a dialog I show on start with

Screen.instance.messageBox()

? how could I preserve the choice after the app gets closed?

also trying to make the icons a set size in my menubar but failing, I'm doing

.menubar-button .icon {
            width: 26;
            height: 26;
        }

but the icon is still giant