Not able to add Child Element to a Window Element - npm run start throwing error.

[joshi-ankur]

@parro-it , @mischnic , @kusti8

So i just started working on building a proton-native desktop app on Windows 10 Pro edition.

I started off with the official documentation and my boiler plate code was ready.

npm run start was working fine and i was able to see . Below is the attached image.

Now when i add a Box Component inside my Window component and try running the npm run start command, it fails :( . Have attached the image below for the same.

Kindly help, i really need this to get working, am i doing something wrong?

[mischnic]

The Button needs to have the onClick prop (not onClicked).

@kusti8 There should be a better error message.

[joshi-ankur]

@mischnic thanks for that change, i updated it. But then it is not solving my problem, i am still getting the same error mentioned above.

Kindly advice. Attached below is the image after updating the prop u mentioned.

[mischnic]

But then it is not solving my problem, i am still getting the same error mentioned above.

It's a different error (the line before the colored lines):

Window and Group only take one child!

Not sure why though.

[joshi-ankur]

@mischnic @kusti8 @parro-it Can u please help me with a workaround to solve my problem? I need to get this desktop app up and running for my client.

[joshi-ankur]

@mischnic yes it is a different error.

Window and Group only take one child

[JVictorV]

@joshi-ankur try to delete the "{ }" at the line 7

[parro-it]

@joshi-ankur could you post the source code as text?

[maciek134]

@joshi-ankur If you still need help with that, a good practice is to provide the source code for a minimal app that would reproduce this bug, nobody will retype everything from the images (in which the code is cropped btw so we can't even see some of it).

[Oxymoron290]

I was getting the error Window and Group only take one child! because I had a comment inside the Window tag...

Removing the comment inside of the window tag resolved my problem

[Oxymoron290]

[kusti8]

Proton Native V2 is now released! If the issue still occurs in the new update, please open a new issue.