TPlannerMaskDatePicker: Two small issues.

VCL TMS VCL UI Pack
1

Hello,
I encountered two issue while using TPlannerMaskDatePicker:

  1. The more serious one is, that if the component is modified and empty, you can't leave it. For example if you simply put it on a form, open the form, select the component, type something and then delete everything, it is impossible to change the focus, which is very awkward.
  2. If you add a bitmap containing more than one glyph as a glyph, only the first one is recognized. The usual button-handling of glyphs doesn't seem to be implemented ("numglyphs" exists, but doesn't seem do anything). Normally you can just load a bitmap with two glyphs and you've got the correct behavior with enabled/disabled.
2

  1. When you compile in debug mode, the IDE is catching all exceptions and will show these. Otherwise, this is a gracefully handled exception when there is no valid date entered and you can control the behavior via the event handler OnInvalidDate.

  2. Try setting PlannerMaskDatePicker.Button.NumGlyphs before setting the button glyph

3
  1. Unfortunately doesn't work this way. I managed to supress the undesired behavior by setting "modified = false" in the KeyUp-event, but that is a rather cumbersome workaround. Interestingly the DB-variant of the component behaves correctly and doesn't require a workaround.
  2. Doesn't work either. I might be overseeing something but "numglyphs" doesn't seem to be used for anything in the source code.

At this opportunity, I also encountered two issues with TPlannerDBMaskDatePicker:

  1. If the current underlying date-field has a value and you perform an append or insert on the dataset, then the component still displays the value of the former record although the current value in the new record would have to be NULL. Changing records with next/prior works though.
  2. While editing the component often flickers. It seems that the former value of the component is displayed for a very short time when it flickers.