this is especially useful for when you want to pass values to custom components from xml, but dont want to setup getters / setters, using above you can just do:

euhm; Implementing Enter to get it to set the text data of a Textfield with correspoding events is getting chaotic; So why does textfield not call UIEvent.CHANGE ? is it because we use invalidation data ? What is all the invalidation and how does it affect setting of Data ? There is a line in the TextField.hx to dispatch the ui change but when uncommenting it breaks the textfield(i.e. the data in all textfields are null or disapear).

textfield should dispatch a UIEvent.CHANGE doesnt it??

nope

it doesnt

line 279 in TextField.hx in core

ok, thats defo wrong then... leave it with me, ill have a bit of a play tomorrow / tonight

ok good. Thanks for the support

Can anyone give an example use for DataSource transformer. I initially thought that it can't be used for what I wanted to do but after looking at the code I can't imagine it working for anything. DataSource get takes an item from backing container by index and then transforms it which would mean that backing container should contain non-transformed values. Few lines lower indexOf transforms the argument first and then tries to find it using transformed valued which would indicate that backing container transformed values.

I have an example. Will share when I am on dev station

Does HaxeUI have drag and drop like capabilities?

You mean, does it have a drag and drop interface designer?

If that's indeed your question, the answer is no, HaxeUI is "only" a library - But a form designer resembling Java Swing / Lazarus / Visual Basic would be amazing!

Perhaps one of the talented folks of the Haxe community already provided something like that?

No, I didn't mean a designer - I'm just looking for ways to implement drag and drop for my own app which I'm finding isn't so trivial

If you feel like implementing it, sure, it's totally possible

That's a given for anything, but I wouldn't want to do that if it already exists somehow.

It's not completely evident, ya'know? I'm not trying to create my own containers/components if I can avoid it . . . but the events I feel like I'd need to be using from a high level don't exists in obvious existing containers/components that I'd probably want them to be in

I guess you wouldn't need a custom container for that

The trick would be to add a component or bundle of components which are already in HaxeUI with generic data where the user clicks after he's selected the desired container in a list

At least that could be a starting point

That's a good idea!

At least for a rough draft

Yay! Glad I could help! :D

Once you've done that it's up to you to decide which properties of the containers you leave editable by the user

Apparently I was having trouble because I was using mouse events from the wrong library . . . well damn. You'd think Haxe being statically typed would catch that sort of thing lol

oh well.