Posted
on Jan 4, 2012
(permalink)
Thanks, Ivan.
I have since found the documentation, particularly the sections that list the various methods and properties available for the controls. Let's take the RadButton API Reference: http://www.telerik.com/help/winforms/allmembers_t_telerik_wincontrols_ui_radbutton.html
Here is what it says about the ButtonElement property:
"Gets the instance of RadButtonElement wrapped by this control. RadButtonElement
is the main element in the hierarchy tree and encapsulates the actual functionality of RadButton." (This is nice and short, but almost as vague as can be when you can see all sorts of functionality that exists parallel to the ButtonElement property).
The API Reference is also showing all sorts of properties of equal hierarchy with ButtonElement, like Top, Bottom, Size, Style, and on and on...... The write-up on ButtonElement says ButtonElement "encapsulates the actual functionality." If Shape is a functionality, I would think Size and Style would be, too, yet Size and Style are not buried beneath ButtonElement like Shape is. Basically, I am having an issue getting a grip on the organizational structures and am finding myself quite lost trying to navigate through them.
So, not really understanding this, I am sure I will try to extend by
analogy the example you gave and start keeping an eye out for
radScheduler.SchedulerElement and radOtherControls.OtherControlsElement.
Exposing the logical pattern would help a newbie get around more efficiently, or at least it would help me ;-)
Is there anything in the documentation that would help me get my hands around this? My issue appears not so much to be a programming one, but rather not understanding the organizational structure of the elements and the patterning that is likely largely repeated from one to the next type of control.
Thanks.
(P.S., Sorry if I am dense-sounding). The idea is I am not the "programmer" on our project, although I know a lot about what programmers do and how they go about it. I am wanting to evaluate Telerik, and if I can get acquainted with its controls' methods and properties, I'll be able to know what we can and cannot do with it.
.