The amount of bugs I've come accross, Most of them I have found work-arounds but I've stumbled across one in-which I just wasted 5-8 hours figuring out that IT WAS A CONSTRUCT BUG.
I'm not at-all saying it's freaking easy to make construct but damn I've come across at-least 10 bugs which have took at-least 30 minutes trying to figure out it was a construct fault.
Answer me this Ashley and Tom, Now I don't mean to be unprofessionally stuck-up but why in the world did you begin C2 without fixing the most atrocious bugs in C1 first? It's unbelievably annoying to me having come across these half-unbearable bugs and it's such a waste of my damn time.
I will first post the 1 bug that is unbelievably ruining C1 and then the one that strikes me back from designing the game I want.
1) When I use the sprite-editor and load up an existing image file and save it, it cuts the image literally in half, it cuts the bottom half of the image completely off. I don't use families or nothing, a completely new inserted sprite.
2) I even created a new blank game just to check this. Whenever you add items to an inserted combobox, when it comes to the user clicking on the box wanting to select an item, It just closes as soon as you click it. It's got in the way of my game and wasted 5-8 hours of my time figuring this out.
Not to sound like an ass-hole Ashley and Tom, But you need to fix these bugs, Sorry if I did sound rude but damn.. why start the 2nd version of something when the first is like... unbearably unbelievably atrociously buggy.
I've gone through about 10-20 bugs in my first day of using Construct Classic.