# haxe-ui
- b
bright-gpu-74537
08/01/2021, 8:38 AMworks exactly the same (ie, fine) on ubunutu (no coconut) - b
bright-gpu-74537
08/01/2021, 8:47 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);var button = container.addComponentAt(new Button(), 1); button.text = 'New Button'; button.onClick = function(_) { trace('bob'); }" /> <button text="add" onclick="container.addComponent(new Button()).text = 'Button ' + container.childComponents.length" /> <button text="remove" onclick="container.removeComponentAt(1)" /> </hbox> - b
bright-gpu-74537
08/01/2021, 8:48 AMbingo... i get a crash (windows) and presumably linux too... - b
bright-gpu-74537
08/01/2021, 8:48 AMnot sure if its the same issue, but there is certainly a bug there - u
user
08/01/2021, 8:49 AMNot sure I follow exactly because my allergies are kicking hard this morning, but I'll check if my fix fixes that, if it doesn't it's probably another bug °° - b
bright-gpu-74537
08/01/2021, 8:49 AMyeah, defo something up there regardless - u
user
08/01/2021, 8:50 AMWorks fine with my patch - b
bright-gpu-74537
08/01/2021, 8:50 AMand breaks without? - u
user
08/01/2021, 8:50 AMI suppose, let's see - u
user
08/01/2021, 8:51 AMSo uh segfaults when I do test then remove (or test again) - u
user
08/01/2021, 8:52 AMI'll re-check doing that with my patch - u
user
08/01/2021, 8:52 AMYeah, fine with my patch - b
bright-gpu-74537
08/01/2021, 8:52 AMyeah, its the second click on test which kills it - b
bright-gpu-74537
08/01/2021, 8:53 AMso something to do with remove components that have an event listener - b
bright-gpu-74537
08/01/2021, 8:55 AMOK, i can see what is happening, i actually think i introduced this recently - u
user
08/01/2021, 8:56 AMThat was one of my first haxeui+coconut bugs so maybe not that recently - b
bright-gpu-74537
08/01/2021, 8:56 AMright - u
user
08/01/2021, 8:57 AMYou did change something there recently but it had no impact - u
user
08/01/2021, 8:57 AM(invert destroy and unregister iirc) - b
bright-gpu-74537
08/01/2021, 8:57 AMoh, yeah, you are right... removeCompontAt is different to removeComponent - b
bright-gpu-74537
08/01/2021, 8:57 AMin the sense when it calls the backend... - b
bright-gpu-74537
08/01/2021, 8:57 AMtotally different place... - b
bright-gpu-74537
08/01/2021, 8:58 AMthose two functions are far far too different actually 😮 - u
user
08/01/2021, 9:05 AMNot so far with my patch,but it's not tested against different targets/use cases - u
user
08/01/2021, 9:07 AMCould even maybe go further and factorize it now - b
bright-gpu-74537
08/01/2021, 9:40 AMwell, im not going to use your PR as i dont think its a good idea to roll up removeComponent and removeComponentAt into the same code - b
bright-gpu-74537
08/01/2021, 9:40 AM(ie, remove the handleRemoveComponentAt call from the backend) - b
bright-gpu-74537
08/01/2021, 9:41 AMbut doenst stop the fact that on hxwidgets removeComponentAt is bugged (its fine on other backends) - b
bright-gpu-74537
08/01/2021, 9:49 AM@User - should be fixed in latest haxeui-core - i think i might refactor it out a little more, but for now, let me know if that fixes it - u
user
08/01/2021, 9:52 AMOnly haxeui-core?