I've found a handful of problems using C1 in a multi-window UWP app. I would say multi-window UWP applications are uncommon and C1 clearly did not think to test their controls in one. That's OK, and I did get a hotfix build once for my first problem, but others have been outstanding for over a month. That hotfix build came from public support too, not private support which is what I'm complaining about. I feel like I get ignored by private support, and even "You will receive a response from one of the ComponentOne staff members via e-mail in 2 business days or less" is untrue.

Support is mostly good if they'd just be a lot more responsive. A simple "we're looking into it" would be far better than silence.

I'm working as a Software Developer for nearly 10 Years, started with Basic and Cobol to C# and .Net since Oktober. Starting with this new job i used Component One WPF Studio and honestly it's the worst library i have ever used in my whole life. You know, when something is not working as it should be i'll say "oh damn you component one" - the sad thing there: 5 times out of 10 it's correct. 3 Times it's .Net and 2 times it's my mistake.
So if you want to improve your quality: Employ Professional FullTime Software Testers. Your customers should not be Beta Testers

greetings
Daniel