there isnt in built, but i dont think it would be too much effort to subclass TableView and add editing abilities to it

... ... but nothing out the box as of yet

Ok, thanks.

Turns out it somewhat works already. Item renderer registers UIEvent .CHANGE handler and calls setProperty, Checkboxes act a bit weird but textfield are fine.

oh yeah, actually, that makes sense... kinda forgot about that... any component that registers CHANGE will update the property that created it

can you open an issue about the checkboxes? Dont really have time to look right now, but minimal test case would be useful if something is off

Created an issue for checkboxes, it can be observed in haxeui.org listview component example and the table example you linked above.

Any advice for modifying Item renderer? Is it supposed to work, should I use ItemRendererFunction or ItemRendererClass instead?

do you have an example?

I define my itemrenderers in xml and add them through code:https://github.com/mundusnine/haxeui-kha-extended/blob/master/haxe/ui/extended/FileBrowser.hx#L26

Adding Item renderer through code first time isn't a problem. I have a table and as a result of user interaction new columns can be added or removed. I was able to header react correctly but content gets stuck with old columns.

Finally found the code responsible with instantiating item renderers, with that knowledge I should be able to get it working.

It seems to be related how item renderer instances are reused, they aren't invalidated when changing item renderer, will create an issue with more detailed description.

@User Coming back on ScrollView on HTML5. I see two components in childComponents that are a Box and a VerticalScrollView. I did not add them. Is it normal?

hmmm, listview will create a content container... not sure scrollview should though... do you have an example you are using? Ill check it out... wont be for a few days though as im refactoring something and have totally knackered haxeui-core in the process 🙂

Yeah I can probably extract something out

thanks

What is the recommended way of distinguishing CHANGE event caused by user interaction and event caused by changing component state using code? I don't want my event handler to trigger when I initialize the values. * Is there way to distinguish between the two cases or subscribe to desired one? * If not, is there a way to temporary disable event triggering? * In the worst case I track software update on my side. It seems that CHANGE event for checkbox doesn't get triggered immediately, but instead gets triggered later when I switch to the page containing it and it gets displayed. This makes use of approaches 2 and 3 problematic.

you could use "click" and "change", i guess that would work... though i think setting state shouldnt have any effect in your app (personal opinion maybe) but setting the state of the, say, checkboxes and that firing events to change said state should make sense, no?. That said, "It seems that CHANGE event for checkbox doesn't get triggered immediately, but instead gets triggered later when I switch to the page" seems like an issue, what do you mean by "page"? Any chance you could open, another, issue? Ill be going on a bug hunt in the next few days

By page I meant tab view.

cool - ill have a play, nice one

@User Is there a way to know when a child component was added to a parentComponent. I.e. I want the child to get a reference to a parents component when it gets added.

onChange probably works but would be called everytime which is not desired. I was searching for something like onParented or sometime like that.

@User Which backend?

kha; But this would be bakcend agnostic

Yeah, I hear ya.... was just thinking about backend specific things you could do for the moment.

Or, if onChange Does fire when adding a child, you could check numComponents prop to determine if it was an add that triggered it.

onChange doesnt fire. I did something else in the meantime.

just about to head to bed, and missed this

what about

UIEvent.READY

?