I think VSGUI does the job perfectly. I have built GUIs using gdi, xiscle, mfcgui, Qt in the past. I find all gui kits the same. All controls will be custom anyway, so why does the gui kit matter? Vstgui is a nice crossplatform wrapper for drawing functions and does it in the simplest possible way. By just drawing inside a window. How can this be slower than anything else? One problem that I did had to solve in vstgui was mouse locking behaviour. Other than that it is the best IMHO so far. I have built complex controls with it. Graphic handlers like on waves eq plugins, alpablended and overlapped controls, realtime graphs, etc, everything with key input. Never expect the kit to solve your gui design problems. It's just a kit with some examples of controls. Any professional control still has to be built from scratch. You still have to design and implement it. The kit or the OS or whatever is irrelevant. I have heard enough people complain about somebody else not doing their job for them. That will never happen in this world. Take a look at the vstgui source, try to understand it, be prepared to spend time in the design process, spec everything, and perhaps fail (some people just cannot do it). Start with CControl and the world is at the end of your fingertips. Some will quit. Some will reach the end with a professional gui framework, no matter what they started with. I have worked with Qt and although is supplies some power in things irrelevant to gui or drawing, it still takes more work than vstgui to do a control.

If you are into gui kit switching which is becoming a sport, think again. The gui kit does not matter.

just my 2 euro cents.

_