# haxe-ui
- b
bright-gpu-74537
11/07/2021, 8:47 PMsure - n
nutritious-father-64388
11/08/2021, 4:49 AMdoes hxWidgets needs any special way to create windows from different threads? - n
nutritious-father-64388
11/08/2021, 4:49 AMopening a dialog from a different thread causes a crash - b
bright-gpu-74537
11/08/2021, 7:41 AMhmmm, ive never tried, but generally you'd want to keep all the UI stuff in the same thread - b
bright-gpu-74537
11/08/2021, 7:42 AMwhy are you opening a file selector from a thread? If its because its long processing surely you'd want to open the file from the main thread (and block the UI in the process) and when you have the file / data process that in another thread, no? - b
bright-gpu-74537
11/08/2021, 7:57 AMfrom wxWidgets: > When writing a multi-threaded application, it is strongly recommended that no secondary threads call GUI functions. The design which uses one GUI thread and several worker threads which communicate with the main one using events is much more robust and will undoubtedly save you countless problems - e
early-truck-71225
11/08/2021, 9:00 AMWhy I get errors here? The path is correct. I did the same with the main view and I don't get any error - b
bright-gpu-74537
11/08/2021, 9:08 AMwhat are the errors? - b
bright-gpu-74537
11/08/2021, 9:08 AMcould be VSCode language server - b
bright-gpu-74537
11/08/2021, 9:09 AMdoes it compile on the command line? - b
bright-gpu-74537
11/08/2021, 9:09 AMCopy codeI was having a lot of macro-related compiler errors in haxeui... but I "fixed" it by just disabling the compilation server in VScode I know it's been brought up before, and it doesn't seem like an easy thing to fix. But man I could not compile twice in a row without an error In my settings.json, I put "haxe.enableCompilationServer": false and that's it. Hope that helps someone else Your compiles will be a second slower but you won't waste 30 seconds crashing and restarting the compilation server anyway And you keep macro'd code completion, since that's a separate thing - e
early-truck-71225
11/08/2021, 9:11 AMNo - e
early-truck-71225
11/08/2021, 9:12 AMIt says: "called from here" - b
bright-gpu-74537
11/08/2021, 9:12 AMon the command line... whats the full output? - e
early-truck-71225
11/08/2021, 9:13 AMIn the MainView.hx, I want to add the view as a child, but it says that it has too many arguments - b
bright-gpu-74537
11/08/2021, 9:14 AMright, generally haxeui custom components dont play well with constructor arguments... there is some code to allow for it, but it might be breaking... - b
bright-gpu-74537
11/08/2021, 9:15 AMif you change the constructor arg to have a default value (null) does it work? - b
bright-gpu-74537
11/08/2021, 9:15 AM(though it might also now break in other ways) - e
early-truck-71225
11/08/2021, 9:16 AMWith 0 arguments, the build error is still there - b
bright-gpu-74537
11/08/2021, 9:17 AMcan you create a minimal repro and send it here? Ill take a look - e
early-truck-71225
11/08/2021, 9:19 AMI added
in the new function and the error is no moresuper(); - b
bright-gpu-74537
11/08/2021, 9:19 AMoh yeah, that error is right there in the screen shot you posted 😄 - e
early-truck-71225
11/08/2021, 9:20 AMBut it's weird, in the MainView.hx file I also extend VBox and I don't have to use super - b
bright-gpu-74537
11/08/2021, 9:20 AMyou must have to use super surely... otherwise things will go very wrong - b
bright-gpu-74537
11/08/2021, 9:21 AMdo you have a constuctor in MainView? - b
bright-gpu-74537
11/08/2021, 9:21 AMif you do, im pretty sure you have to use super... i wouldnt expect it compile otherwise - b
bright-gpu-74537
11/08/2021, 9:22 AMalthough, VBox does have its own "new" so thats probably why... but still, i would expect issues... is MainView.hx using a build macro? - e
early-truck-71225
11/08/2021, 9:22 AMIt works without the super constructor - b
bright-gpu-74537
11/08/2021, 9:23 AMthere is a "super" there - e
early-truck-71225
11/08/2021, 9:23 AMOh, yeah, sorry, I'm stupid