# haxe-ui
- b
bright-gpu-74537
07/31/2021, 2:25 PM... also you can (currently) do things like:container.addComponet(new Button()).text = "{{string1}} {{string2}} something {{string3}} and {{string4, someComponent.value}}" - b
bright-gpu-74537
07/31/2021, 2:26 PMwhich will also work (currently)... so, it needs something to happen at runtime - u
user
07/31/2021, 7:25 PMI know how to reproduce the segfault now, it's not linked to scroll at all - u
user
07/31/2021, 7:26 PMIt's when I change state in an onClick, resulting in the component on which onClick was called to be disposed of Doesn't seem to be related to my PR but will keep looking for the thing that triggered it.. - u
user
07/31/2021, 8:43 PM... ok nvm It's a previous fix in haxeui-core for wxwidgets that I removed because you seemed to have fixed it in master, but it's still needed - u
user
07/31/2021, 9:07 PMNice and all, but still doesn't allow me to scroll parent view when cursor is over the slider >.> will have to try to improve that another time.. - b
bright-gpu-74537
08/01/2021, 6:58 AMwhats the fix? - u
user
08/01/2021, 7:00 AMhttps://github.com/kLabz/haxeui-core/commit/335fa0b95c65ec6df11463f57cffb9b7ee92dd82 Using the same order as removeComponent() This makes handleRemoveComponentAt() useless, too - b
bright-gpu-74537
08/01/2021, 7:01 AMhmmm, yeah, im not sure about that PR - b
bright-gpu-74537
08/01/2021, 7:02 AMbecause it makes removeAt the same as remove... and there may be framework reasons to use removeAt "properly" - u
user
08/01/2021, 7:02 AMYeah.. - u
user
08/01/2021, 7:03 AMBut I'm not sure it works at all - b
bright-gpu-74537
08/01/2021, 7:03 AMso whats the underlying reason for the segfault? - u
user
08/01/2021, 7:04 AMChild is removed, then is retrieved by index (which by then is wrong), some things like that - b
bright-gpu-74537
08/01/2021, 7:04 AMhmmm, right, ill try this end sans coconut and see what happens, could be that its just a bugged function - u
user
08/01/2021, 7:05 AM
doesn't make me think this part is tested with edge cases too :Pif (_children != null) - b
bright-gpu-74537
08/01/2021, 7:05 AMi think the _children is just a typo / copy-pasta - u
user
08/01/2021, 7:06 AMYeah most likely - b
bright-gpu-74537
08/01/2021, 7:12 AMCopy codexml <hbox id="container"> <button text="Button 1" /> <button text="Button 2" /> <button text="Button 3" /> </hbox> <button text="remove" onclick="container.removeComponentAt(1)" /> - u
user
08/01/2021, 7:14 AMI get the segfault when I remove the component at 1 and add another there iirc - b
bright-gpu-74537
08/01/2021, 7:17 AMCopy codexml <hbox id="container"> <button text="Button 1" /> <button text="Button 2" /> <button text="Button 3" /> </hbox> <hbox> <button text="add" onclick="container.addComponent(new Button()).text = 'Button ' + container.childComponents.length" /> <button text="remove" onclick="container.removeComponentAt(1)" /> </hbox> - u
user
08/01/2021, 7:26 AMAt the same time - b
bright-gpu-74537
08/01/2021, 7:27 AMat the same time? You mean remove(1) and add(new Button()) in the same handler? - u
user
08/01/2021, 7:27 AMaddAt(1) yeah - b
bright-gpu-74537
08/01/2021, 7:27 AMaddAt... right - b
bright-gpu-74537
08/01/2021, 7:31 AMCopy codexml <hbox id="container"> <button text="Button 1" /> <button text="Button 2" /> <button text="Button 3" /> </hbox> <hbox> <button text="test" onclick="container.removeComponentAt(1);container.addComponentAt(new Button(), 1).text = 'New Button'" /> <button text="add" onclick="container.addComponent(new Button()).text = 'Button ' + container.childComponents.length" /> <button text="remove" onclick="container.removeComponentAt(1)" /> </hbox> - u
user
08/01/2021, 8:32 AM🤷♂️ am getting a segfault for similar things - b
bright-gpu-74537
08/01/2021, 8:35 AMill try it on the vm - u
user
08/01/2021, 8:35 AMMaybe coconut is doing something slightly different, I didn't test this yet without it - b
bright-gpu-74537
08/01/2021, 8:36 AMyeah, might make sense to see if it happens without coconut