Haxe

i'm not intimately familiar with ceramic's loading and scene management system

i delved into it a while ago but not completely

You can override the scene load() method and call the callback after running a Timer.delay()

can you please give an example of how i would update my scene layout on resize?

would i need to explicitly resize my scene size or something like that? im not exactly sure

pretty sure i noted this before but pointerUp doesnt seem to work

almost got a functional dropdown menu, one more bug

`pointerUp` event on a visual will only be triggered if you are listening to `pointerDown` as well, and that `pointerDown` has triggered on this visual

Well, you can override `resize()` method of your `Scene` and do whatever you wish with your `width` and `height` properties

I'll have to double check but updating the scene width and height to the new window actualWidth and actualHeight didn't do anything

I tried onResize for the app.screen and scene, neither worked

<@459463405636419594> The scene is already resizing itself automatically (as long as you assigned to `app.scenes.main` or `app.scenes.set(...)`, but of course you need to take care of what's inside, using the new scene's width and height

<https://github.com/Jarrio/haxeui-ceramic/blob/master/haxe/ui/backend/ScreenImpl.hx#L67>

the event is created in the constructor of the file

in `Visual.hx`
```hx
#if ceramic_no_depth_range
    public var depthRange(default,set):Float = -1;
    #else
    public var depthRange(default,set):Float = 1;
    #end
    function set_depthRange(depthRange:Float):Float {
        if (this.depthRange == depthRange) return depthRange;
        this.depthRange = depthRange;
        ceramic.App.app.hierarchyDirty = true;
        return depthRange;
    }
```

where can I change `ceramic_no_depth_range`?

That’s a flag to use legacy behavior, mostly related to a game that was using Ceramic before depthRange was defaulting to 1. Why would you want to change that define though? You can always set depthRange on a visual at runtime

But anyway you can enable that define like any other defines in ceramic.yml

i was wondering why the depths seemed to be behaving oddly and that line was indicated as having no effect


https://cdn.discordapp.com/attachments/853414608747364352/1105964831728742440/image.png