Quote Originally Posted by wysota View Post
You know, I wanted to say that right in the beginning - why do you want to hide a property in Designer? This won't stop anyone from using it in code anyway, so what's the point? If you want to disable all the properties (only in Designer!) then the proper way to go is to implement a QDesignerPropertySheetExtension for your widget - this will substitute the default property browser with yours. You can specify your own properties there and handle them the way you want. Of course it won't stop anyone from calling the property methods (or QObject::setProperty()) directly from code.

I'm generating a library of custom plugins that will be used by another group (non-programmers) to lay out GUI screens. I'm not real concerned about somebody doing what you said because the intended audience will be non-programming UI designers. I really wish there was a way to add more slots that can be seen in designer, but we can't have everything.