Automatically highlight RuleRequiredValue properties: RuleHighlightMode { None, BackgroundColor, Border, Icon }
Also, it may be useful for other rules as well: for example, immediately highlight an editor if it contains an invalid value.
ValidationHighlightOptions.HighlightAlways.Add( typeof(RuleRequiredProperties));
ValidationHighlightOptions.HighlightAlwaysMode = new RuleHighlightModeBackgroundColor(Color.Red);
ValidationHighlightOptions.HighlightImmediatelyIfBroken.Add( typeof(RuleRangeProperties));
ValidationHighlightOptions.HighlightImmediatelyIfBrokenMode = new RuleHighlightModeBorder(Color.Yellow);
Or:
[RuleRange(…)]
[ValidationHighlightBorder(Color.Red, ValidationHighlightMode.HighlightImmediatelyIfBroken /* default mode */)]
public int Count { … }
[RuleRange(…)]
[ValidationHighlightBackgroundColor(Color.Red, ValidationHighlightMode.HighlightAlways)]
public int Count { … }
Also, provide a way to show requirements of any highlighted property to an end-user (tooltip/hint ?).
See Also:
Mandatory fields
Highlight required field in detailview
Thanks,
Dan
We have closed this ticket because another page addresses its subject:
Validation - Check validation rules when input focus changesValidation - Introduce an immediate visualization for properties, which are marked with the RuleRequiredValue attribute (BackgroundColor, Border or Icon)
created 16 years ago
(modified 7 years ago)
any update on this? thanks kindly…
Any Updates?
Sujan
Hello,
Though I understand that this is a high priority functionality for you, I cannot currently provide you with estimation dates on this feature. We refrain from announcing any specific feature for any product in R&D prior to its release. This is our position for many reasons, including the fact that by promising X or Y, developers end up planning their development schedules around our promised feature set, which can change quite dynamically. We keep this feature on our radar, but it is still premature to discuss when it may be available.
Alexey,
please excuse if I have to become apparent here: This comment after more than five years is ridiculous. I (and all other people who use XAF) am a developer myself. I have customers requensting features. After five years from the request, I would not have to answer or comment anything, because I would no loinger have the customer. I understand that the release process for your product is very complicated. And I do not take this feature for the most important in the category of important features (a workaround exists and everybody implemented it meanwhile, I think).
But the reason you give for a meanwhile five years during implementation of a rather uncomplicated and small feature is really ridiculuos.
Again, excuse my apparent words, I use XAF for many years now and I am very happy to have such a tool and - last not least - an excellent support.
Kind regards,
Markus