there are still some issues im working through, but its getting there

@User will do. still looking at a way to convert ttf to msdf for haxeui

hi, I am looking into using haxe/openfl/haxeui to make a little simulation for a school project. I am wondering if it is possible to use haxeui "on top" or "to the side" of a game/simulation. in other words, is it possible to write a game with traditional openfl methods, then add a ui with haxeui, where haxeui wouldn't replace the visuals of the game? i have been looking around and all haxeui examples i see seem to be the entirety of the app.

sure, should be possible... haxeui (when using it with openfl) components just end up as openfl sprites... so you can put them anywhere you want

awesome, thanks for the confirmation.

np, let us know how you get on 🙂

@User

Called from hxcpp::__hxcpp_main
Called from ApplicationMain::main ApplicationMain.hx line 25
Called from ApplicationMain::create ApplicationMain.hx line 130
Called from lime.app.Application::exec lime/app/Application.hx line 150
Called from lime._internal.backend.native.NativeApplication::exec lime/_internal/backend/native/NativeApplication.hx line 146
Called from lime._internal.backend.native.NativeApplication::handleRenderEvent lime/_internal/backend/native/NativeApplication.hx line 370
Called from lime.app._Event_lime_graphics_RenderContext_Void::dispatch lime/_internal/macros/EventMacro.hx line 91
Called from openfl.display.Stage::__onLimeRender openfl/display/Stage.hx line 1950
Called from openfl.display.Stage::__broadcastEvent openfl/display/Stage.hx line 1166
Called from openfl.display.DisplayObject::__dispatch openfl/display/DisplayObject.hx line 507
Called from openfl.events.EventDispatcher::__dispatchEvent openfl/events/EventDispatcher.hx line 178
Called from flixel.FlxGame::onEnterFrame flixel/FlxGame.hx line 545
Called from flixel.FlxGame::step flixel/FlxGame.hx line 677
Called from flixel.FlxGame::update flixel/FlxGame.hx line 724
Called from flixel.FlxGame::switchState flixel/FlxGame.hx line 624
Called from flixel.FlxState::destroy flixel/FlxState.hx line 134
Called from flixel.group.FlxTypedGroup::destroy flixel/group/FlxGroup.hx line 149
Called from haxe.ui.backend.ComponentImpl::destroy haxe/ui/backend/ComponentImpl.hx line 924
Called from haxe.ui.core.Screen::removeComponent haxe/ui/core/Screen.hx line 50
Called from haxe.ui.backend.ScreenImpl::removeComponent haxe/ui/backend/ScreenImpl.hx line 171
Called from flixel.group.FlxTypedGroup::remove flixel/group/FlxGroup.hx line 410
Called from flixel.util._FlxSignal.FlxSignal1::dispatch1 flixel/util/FlxSignal.hx line 284
Critical Error: Uncatchable Throw: Null Object Reference

I had just updated haxeui-core and flixel and this happened

oh? :/

can you isolate it to something small / specific. Any other haxeui-flixel users get the same with latest? It seems to be something related to switching state?

I just created a state, created a button, and in it's click I switch to another state which has haxeui stuff as well.

^^ OK, well, i can confirm the crash this end, just want to see what commit borked it

@User - should be fixed now

git haxeui-flixel, i fixed another (unrelated) issue in core, so you might wanna grab that while you are there

having some problems with tooltips on menubar buttons

maybe related: I'm using the tooltips by adding

tooltip="Tooltip text"

to the xml of the element

they way you are adding them is fine

ill check it out

No rush Ian, but was wondering whether those changable labels that you showed off in that file tree renaming demo were open source, or whether you had any tips for implementing that? Help Fat Leech and prioritise other work, this is unimportant 🙂

@User - can you try that again? (latest core / backend)... issue was that the menu was being shown over the tooltip

@User - the treeview is a little tied to haxe studio now, but its pretty easy to do: basically, have an text field that will be displayed over the top and will take the size of the item being edited

Tree's fine, this is for layer renaming 🙂

is the layer view a listview?

Yup, pretty sure.

ill have a think... i wonder if its worth having something like this on core... EditableListView or, listView.editable = true

(same for tableview)

That'd be very useful, but surely having some editable label would be generic to both?

well, it could be done in the item renderer... but i wonder if it would be more efficient to do in the component itself - not sure

ill have a think / play

@User - ive also fixed the issue with the "double selection" that is shown here: