Well, I shouldn't jump in, but it's Friday and I'm coasting a bit, so I will.

I use the SSTab for data entry screens all over the place, and I love them and my users do too. I'm bewildered as to what the problem is.

Wqweto, I like much of the code you've written around here, but we've got to agree to disagree on this one.

Quote Originally Posted by wqweto View Post
I see you point. Unfortunately this does not work for me or any other professional, because we can't be bothered to use `SSTab` control only because it's easier for us devs to implement it and in the processes end up with a solution that makes our end-users lives miserable.
If we push those thoughts to their logical conclusion, we may as well return to using Notepad-type code editors because they allow us maximum flexibility to write the best code for our users. Also, I'm not sure that making things easier for coders and making them easier for users is an antithetical tension. I will agree that that's true in some cases. For me, the idea of bound controls comes to mind, which I can't stand (although I suspect there are those who will even disagree what that).

However, ideally, ease for the coder and easy/intuitive programs for the users can rise in a mutually beneficial way. I certainly believe that the ability to design forms via select-and-draw from the ToolBox is an example of this. I'd hate to think that I'd have to write all of my form-design code in notepad.

For me, a tabbed dialog that's WYSIWYG at design time is a natural extension of this.

People may point out that the SSTab can't be themed, and is looking somewhat dated, but those aren't concerns to me. For my application, I'm much more concerned with user functionality and ease of design. And the SSTab provides both of these in spades (IMHO).

To All, Have a Great Weekend,
Elroy