1.5 is like 6 months out of date at this point... 😮

hm.. ok that seems to be a trend in haxe, even haxe it self has not had a release in almost a year

thing is i try to keep things somewhat stable, and that has been hard with all git versions 😄

well, you dont have to update the git... you can just manage it all locally

but either way, 1.5 is woefully out of date at this point...

sure, but if someone else want to compile my code it becomes a problem, and if the API has changed between my gitclone and whats on master when someone else try to build it its not gonna work

i always say im going to release like monthly, but it never happens, there is always "one more thing" i want to squeeze in...

yeah, this is true

git sub modules?

do you happen to know if the openFL can do native windows ? it would be nice to be able to create something that supports multi monitor use

i think it can, but i dont know how well it does it

i know there have been examples of it done in the past but the example was how it would crash after some time, and sicne then a lot has changed, think it was openFL 7 or 8

probably something i am missing again, i have not added any mouse events yet i get :

less
Uncaught exception: Null access
Called from haxe.ui.containers.windows._Window.Builder.onMouseDown(haxe/ui/containers/windows/Window.hx:327)
Called from haxe.ui.tooltips.ToolTipManager.~stopCurrent.0(lime/app/Module.hx:0)
Called from haxe.ui.util.EventMap.invoke(haxe/ui/util/EventMap.hx:82)
Called from haxe.ui.core.ComponentEvents.dispatch(haxe/ui/core/ComponentEvents.hx:98)
Called from haxe.ui.core.ComponentEvents._onMappedEvent(haxe/ui/core/ComponentEvents.hx:127)
Called from haxe.ui.backend.ComponentImpl.__onMouseEvent(haxe/ui/backend/ComponentImpl.hx:343)
Called from openfl.text.TextField.~this_onMouseDown.2(lime/app/Module.hx:0)
Called from openfl.events.EventDispatcher.__dispatchEvent(openfl/events/EventDispatcher.hx:402)
Called from openfl.display.DisplayObject.__dispatch(openfl/display/DisplayObject.hx:1399)
Called from openfl.display.Stage.__dispatchStack(openfl/display/Stage.hx:1381)
Called from openfl.display.Stage.__onMouse(openfl/display/Stage.hx:2602)
Called from openfl.display.Stage.__onLimeMouseDown(openfl/display/Stage.hx:1948)
Called from openfl.display.Stage.~__onLimeCreateWindow.13(openfl/display/Stage.hx:1783)
Called from lime.app._Event_Float_Float_lime_ui_MouseButton_Void.dispatch(lime/_internal/macros/EventMacro.hx:91)
Called from lime._internal.backend.native.NativeApplication.handleMouseEvent(lime/_internal/backend/native/NativeApplication.hx:338)

i probably need a WindowManager or something

hmmm, shouldnt do... feels like a bug... is your project zippabe and shareable?

sure but is just junk, its just copy pasta example code to see what i can get out of the box

thats fine... i just wanna see what you have done so i can repro

ok, so sorry, yeah, you are right, you dont add windows directly to apps, screen, etc, you use the WindowManager... ... that said, i wouldnt expect it to crash

the only thing more i could wish for is a way to drag a window onto an area to dock it, is there any way for app component to detect a window hovering over it?

so there is no docking at the moment... and its not an easy thing to get right, so its not something im going to tackle any time soon, though i defo would be useful

> is there any way for app component to detect a window hovering over it? i guess you mean a way to detect if one component is over another? I mean, you could see if their bounds intersect, etc

the reason why i am asking is because windows are handled by the widnow manager and not added by the "app"

but yeah, i guess i could get the x,y and bounds and run some calculations when the windows are been draged around

the "app" (HaxeUIApp) is really "nothing" class... its a util class that allows switching between backends easy... its not required at all... and it doesnt have a viewport or anything like that

ok, so this shouldnt NPE now... it should "work"(ish) but you'll also get warnings traced out:

WARNING: this window doenst have a window manager associated with it, make sure it was added via WindowManager.instance.addWindow

@early-butcher-76809 - you are using haxeui-heaps with a custom bitmap font... correct?

I do use a custom font, yes

any chance i could grab it? (and any others you have)... someone is having some problems with fonts ( https://community.haxeui.org/t/custom-bitmap-font-causes-texts-to-be-upside-down/507 ) and id like to build up a repro with as many examples as possible so i know if ive broken anything

Hey, that was the issue I used to have :D

Until you made me use ``SDFFonts.register(file.entry.path);`` somewhere