09 Jan 2005
Link to this post
22 Oct 2012
in reply to
I've got a long list of issues I've been hoping to see addressed, but I guess top of my list are a couple that I've tried submitting as suggestions and even to PITS, but never seem to go anywhere.
1. Provide an option for FieldControls (e.g. ImageField) to open their client 'selector' dialog in 'pop-up' mode, rather than only allowing an embedded dialog.
The reason for this is that they are often next to useless when used in a Control Designer, as the embedded nature means that you are forced to re-size the containing dialog (which is the main property editor) and that is often next to impossible if it's larger than the FieldControl dialog... creating an ugly, confusing mess of one dialog partially overlaying the other.
2. Make the various client APIs (e.g. FieldControls) consistent and complete, and DOCUMENT it !!
As an example: The PageField control has events for Opening and Closing the selector dialog, but the ImageField does not. The means you are forced to 'fake' it, by subscribing to multiple dialog element events (e.g. button clicks) and it is not totally reliable.
As another example: The various get_<item>(), set_<item>() public methods are not consistently available across the API, and (of course) not documented... forcing you to spend far too much time exploring the client objects with a debugger, to try and find out how to do really basic things such as get/set values... and which leaves you open to your code being broken should Telerik change non-published properties/methods in the future.