I’m using the Label property for editor controls and find this to be a very useful feature. I would like to suggest two enhancements, which in my view must be very easy for you to implement (but of course I might be wrong).
1. add the Label property for all controls, not just the editor ones. For example for the Label control. Let’s say I have two DateTimePickers to show the Start and End of an event, which have their Label properties set to “Start” and “End” respectively. I would like to add next to them a Label (readonly) control which would show the duration of the event. It would be very nice to have the Label property of the latter to “Duration” instead of having to add another Label control next to it with a static Text = “Duration”. It would also be much easier to deal with in case of theming or responsive profile changes, since it would follow its parent Label control, exactly as all the other editor controls.
2. Add a second Label-type property for the editor controls. I often have to add another Label under each editor control to show explanations for what is expected to enter in the editor or show validation error messages to the user. It would be useful if this could be shown/hidden if there was a validation error or not respectively.
I’d like to add the showing an error text under a control can be achieved with a property extender. An external component like the ToolTip or the HelpTip or the ErrorProvider that can add anything to any other widget on the client side. Like now the ErrorProvider adds an icon to the target control.
For the embedded Label it’s different because it has to create its own container and layout (see how the editor and label share the same space), and other complex interactions that are quite sophisticated in Wisej.
Hi Alex! I hope all is well and I’m glad to see you back on Wisej.
We may add the Label property to the Label control but it’s not certain. Just adding the Label to the editors has caused a lot of problems because on the client side the editor widget has to be wrapped in another widget which has it’s own set of events and properties and everything has to be split.
Please login first to submit.