# haxe-ui
- b
bright-gpu-74537
05/16/2020, 5:05 PMright - u
user
05/16/2020, 5:05 PMI first used tabbar but since it was not "working" I moved to tabview - u
user
05/16/2020, 5:05 PMnot a real problem - b
bright-gpu-74537
05/16/2020, 5:06 PMyeah, its the correct to control to be using, even in a composite haxeui application, tabview makes more sense that tabbar (in a composite backend the tabview is a tabbar with a stack) - u
user
05/16/2020, 5:08 PMI also fought with optionbox....it wasn't obvious I had to use optionbox1.selectedOption to get the optionbox selected in the group optionbox1 was added - u
user
05/16/2020, 5:08 PMif first tried to get all optionbox of a group and find which one was selected but group.numComponents return 0 😦 - b
bright-gpu-74537
05/16/2020, 5:09 PMhow else would you? You could look for selected on individual optionbox components if you wanted, no? - b
bright-gpu-74537
05/16/2020, 5:09 PMnumComponents = 0 sounds like a bug... do you have some (minimal) xml / code? - u
user
05/16/2020, 5:10 PMI was expecting for group.selectedOption ("which component of the container is selected") - u
user
05/16/2020, 5:11 PMbut i mean group HAS to be a optionBox container, not a vbox or hbox - b
bright-gpu-74537
05/16/2020, 5:11 PMwell, its a group container (iirc) not specifically for optionboxes - b
bright-gpu-74537
05/16/2020, 5:12 PMie, onchange events apply to the container... - b
bright-gpu-74537
05/16/2020, 5:12 PMdo you have small code? - f
fierce-alligator-14675
05/16/2020, 5:12 PMasking a man about the size of his code. ruuuude - b
bright-gpu-74537
05/16/2020, 5:12 PM(rather than the big bug #87 thing) - u
user
05/16/2020, 5:13 PMso you prefer a code per bug rather than my bugs app tester ? 😉 - b
bright-gpu-74537
05/16/2020, 5:13 PM100% - u
user
05/16/2020, 5:13 PMok - b
bright-gpu-74537
05/16/2020, 5:14 PMone bug, one project. It make its so much easier - b
bright-gpu-74537
05/16/2020, 5:14 PMit doesnt have to be that way, but it does mean i dont have to "understand" what your code is trying to do - b
bright-gpu-74537
05/16/2020, 5:15 PMi think someone asked a while ago "is there any major issues with using haxeui", i guess he deleted it before i could answer: documentation - u
user
05/16/2020, 5:16 PMis there a way to define the XML layout on the .hx file ? it would be easier for bug report : one file only - u
user
05/16/2020, 5:17 PMI looked for a way earlier, I'm pretty I saw a sample somewhere but I was unable to find it again 😦 - u
user
05/16/2020, 5:18 PMthis way I could create an github issue with code sample, which seems to be the easiest for you - b
bright-gpu-74537
05/16/2020, 5:21 PM@:xml("") should work, but ive actually seen issues with it... but im not 100% sure its to do with the macros - b
bright-gpu-74537
05/16/2020, 5:23 PMideally the result of "haxelib run haxeui-core create hxwidgets" should create enough of a project to add a bug to - b
bright-gpu-74537
05/16/2020, 6:07 PMnumComponents? Is that a haxeui thing? - b
bright-gpu-74537
05/16/2020, 6:07 PMheh, so it is - b
bright-gpu-74537
05/16/2020, 6:08 PMdoes
give different / better results?group.childComponets.length