First, I realize I can use RadInputManager to eliminate the init function by using plain old asp.net controls.
Now that we have that cleared up, why in the world would you want to make me have to do that?!?! Seriously, I buy controls from a control vendor to make my life easier not to create more work. I need to be able to drop a control from a control vendor on a page, set it properties, and move on to my next task.
You REALLY need to do something to make your controls faster on page load by either not having every control call an init function or making them smart and calling a single init function. And if it is the second option then that single init function had better be fast. I'm at the point where I'm going to have to make a go / no go decision on using the RAD Controls anymore because they are sooooooooooooo sllllllllllllooooooooooooooooowwwwwwwwwwwwwwwwwwwww!!!!!
Now that we have that cleared up, why in the world would you want to make me have to do that?!?! Seriously, I buy controls from a control vendor to make my life easier not to create more work. I need to be able to drop a control from a control vendor on a page, set it properties, and move on to my next task.
You REALLY need to do something to make your controls faster on page load by either not having every control call an init function or making them smart and calling a single init function. And if it is the second option then that single init function had better be fast. I'm at the point where I'm going to have to make a go / no go decision on using the RAD Controls anymore because they are sooooooooooooo sllllllllllllooooooooooooooooowwwwwwwwwwwwwwwwwwwww!!!!!