Ok - it's up check in the for ReferenceLibrary* classes and in

Assets/ui

for the XMLs.

i honestly dont really like this

DropDownBuilder.HANDLER_MAP.set("referenceLibraryDropdownHandler", Type.getClassName(ReferenceLibraryDropdownHandler));

at all

cant you do it in the constructor for the class itself?

just checking color popup

yeah, wouldnt something like that work?

still not a huge fan, but at least its self contained

I can try later to move it and see if that works better sure

will let you know

it should work, i mean, colorpopup uses it

but i dont really like how... "something" that whole system is... i know that at some point i wanted all that to go into the module, but never got round to it

I tried moving the ReferenceLibraryDropdownHandler into the ReferenceLibraryDropdown and moving the handler map update into ReferenceLibraryDropdown.new(). But that gave me the same issue I found before where :

Uncaught exception: Null access .__type__
Called from $Type.createInstance(D:\Program Files\HaxeToolkit425\haxe\std/hl/_std/Type.hx:126)
Called from haxe.ui.components.DropDownBuilder.get_handler(haxe/ui/components/DropDown.hx:940)
Called from haxe.ui.components.DropDownEvents.hideDropDown(haxe/ui/components/DropDown.hx:854)
Called from haxe.ui.components.DropDownEvents.onHidden(haxe/ui/components/DropDown.hx:643)
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.dispatchRecursively(haxe/ui/core/ComponentEvents.hx:108)
Called from haxe.ui.core.ComponentEvents.dispatchRecursively(haxe/ui/core/ComponentEvents.hx:110)
Called from haxe.ui.core.Component.hide(haxe/ui/core/Component.hx:1024)
Called from haxe.ui.core.Component.set_hidden(haxe/ui/core/Component.hx:1170)
Called from haxe.ui.backend.ComponentImpl.set_visible(haxe/ui/backend/ComponentImpl.hx:232)
Called from ui.$UI.__constructor__(ui/UI.hx:179)

This is coming from the place where I am setting initial value for references.visibility to false. That piece of xml is:

<vbox id="references" width="100%">
            <dropdown id="referenceDDId" text="Reference Library" type="referenceLibraryDropdownHandler" styleName="referencesBox" width="100%" />
        </vbox>

This feels like a circular reference. I wonder if this should be structured differently

I suspect making it possible to define the handler type in the module would help.

I have been working on updating a legacy project from AS3 to Haxe. It was built in Flixel, and publish to Android tablets and the iPad using AIR. I wanted to change as little as possible, so update to using HaxeFlixel, and still publishing to AIR using

lime test air -android

. Took a little to setup, but working fine. But I just added HaxeUI for a better UI, but the button taps seem to be a bit off. In my test, I have three buttons aligned vertically. I thought only the top button was working, but that is because the hit areas seem to be much lower than they should be. I know AIR for Android is probably not a popular target, but is this a known issue? Any clues? Or anything I can do to diagnose what is going on a little better?

Ok, so I reimplemented this a bit to make it conform to the color-picker-popup much more closely. I had originally not fully understood how to use it as a model and used the dropdown demos. In any case, the bug above is gone. There are really three parts to a popup: 1. the DropDown subclass, 2. the DropDownHandler subcalss and 3. the DropDownView which basically adds dropdown function to whatever you want. I also inlined the XML pieces to match the color-picker-popup. Not required but it made it easier to see what I done, and it puts everything in one place. Latest code on gh in case you're interested. I guess the only thing this exercise suggests is that it is possible to get this going in a "buggie" way which requires weird registration of the handler. It would be nice if that were harder to do or spat errors.

any chance for your test app? I can try and run it this end and see if the same happens

could be a dpi issue

nice one, ill take a look... fyi, you shouldnt have to subclass dropdown, your original method should have also worked fine, so ill check that out when i get a moment

I found something interesting This works:

haxe
var a = haxe.ui.ComponentBuilder.fromString('<vbox><button text="Button" /></vbox>', "xml");

Thids doesn't

haxe
var oo:String = '<vbox><button text="Button" /></vbox>';
var a = haxe.ui.ComponentBuilder.fromString(oo, "xml");

It says

src/Main.hx:14: characters 45-47 : haxe.macro.Expr should be String

BTW, there still are some references of Toolkit.componentFromString in haxeui core Readme

i think that make sense, i mean, when you are defining a string, that is runtime, the macros operate on expressions at compile time

though, it is confusing i agree

technically, i think you should be using the "RuntimeComponentBuilder" with the variable version

i wonder if you can like "eval" a haxe expr at compile time

After posting , I thought it kind of made sense. I wanted to use it a compile time and just have the string separated to make the code clearer. I can't answer you , I'm not really got at macros ^^

Quick question - I tried getting a change event from one part of the UI (the configuration button group) to update the selected item in the ListView within reference library component in the dropdown. It appears that findComponent() cannot find the ListView by Id when the component is not dropped down - either that or I don't understand how findComponent works ?

so findComponent wont work to find the list of a dropown, since technically its not a child of it

cant you just do .selectedIndex or .selectedItem on the dropdown?

technically the dropdown only has one item