ah I see - I'm seeing it as insecure - non-HTTPs I guess

yeah, i need to regen the docs and make them use https i think... i keep putting it off

I hit it with https and it didn't render so well

so sounds like

Lack of HTTPS can also affect the rest of the website, it prevents the favicon from loading:

HTTPS-Only Mode: Upgrading insecure request “https://haxeui.org/favicon.png” failed. (M21-C12276)

One more thing on the frame > label thing. If I size up the font the frame itself does not expand to accommodate the text so it runs over the end of the box. I'm guessing it's not considered content.

In my use case I can figure that out - early days - it will change anyway - but figured I'd mention it

@bright-gpu-74537 Thanks 🙂

It also seems your HTTPS Certificate is only valid for

www.haxeui.org

and not

haxeui.org

(where data like the favicon lives).

i actually noticed that, i would consider that a bug... kinda

right, will have a play with that too... probably just need to change the URL in the html

never actually noticed there was no fav icon

Well it only breaks if you turn on HTTPS-Only mode, which is off by default.

ah - will have to turn it on to see what breaks

I've mocked up part of my UI, a table for entering equations here http://haxeui.org/builder/?jqtwji and this renders fine in the playground and I can click into any textfield and type stuff. But in my flixel/haxeui program using the same tableview markup as soon as I click in a textfield I get a Null access from the FocusManager. I am assuming that I've not properly initialized something. There are no callbacks linked to any fields yet - just trying to get the layout down. This is the stack

Uncaught exception: Null access
Called from haxe.ui.focus.FocusManager.set_focus(haxe/ui/focus/FocusManager.hx:104)
Called from haxe.ui.core.InteractiveComponent.set_focus(haxe/ui/core/InteractiveComponent.hx:53)
Called from haxe.ui.components._TextField.Events.onMouseDown(haxe/ui/components/TextField.hx:341)
Called from haxe.ui.tooltips.ToolTipManager.~hideToolTip.0(lime/app/Module.hx:0)
Called from haxe.ui.util.EventMap.invoke(haxe/ui/util/EventMap.hx:76)
Called from haxe.ui.core.ComponentEvents.dispatch(haxe/ui/core/ComponentEvents.hx:98)
...

Here's the relevant code

if (value != null) {
            focusInfo.currentFocus = value;    <---- this is L104
            focusInfo.currentFocus.focus = true;
        }

So I guess the question is why is focusInfo null ? Master branch code in haxeui-core shows different code at this point. I'm using version 1.4.0 which seems to be the latest published to haxelib.

ah, you should defo be using git branches at the moment, the haxelib release is already months out of date

heres your app locally (using git branches):

i think there is an issue with the clip rects on haxeui-flixel though... looking at it now

ah, the clip issue is to do with text inputs, since its an openfl text input, and not native to flixel... ... ... thats a pain

this will need some thinking about :/ I guess the most obvious solution is that until focused the text input would be a normal flixel text, and when focused changes to the openfl input... sounds like a headache waiting to happen 😦

(very open to other, less complex, solutions)

frame label issue fixed: http://haxeui.org/builder/?bssobk (frame labels that are > frame contents are taken into account when frames are autosized) I cant remember who found it

Nice

I noticed it was openfl in the stack trace and it seemed a bit odd with the flixel backend

I thought you might say that - I'll try that - should I update backend also ? I guess it all might as well be updated

that sounds problematic to me but then I understand very little at present about how all this hangs together, That said I was thinking it would be nice to be able to use a different widget set with filxel - that would mean a separate backend. I don't know if that's possible but I don't really want to bite that off until I have a flixel based thing running

yeah, you defo want git core + backend (plus any other lib like hxwidgets)

the problem is flixel doesnt have any good text input type components

yeah - kinda saw that