Project JEDI - Issue Tracker
Mantis Bugtracker

Viewing Issue Advanced Details Jump to Notes ] View Simple ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0006648 [JEDI VCL] 00 JVCL Components major always 2018-08-22 09:56 2019-05-12 17:10
Reporter TheBlackfish View Status public  
Assigned To
Priority normal Resolution open Platform
Status feedback   OS
Projection none   OS Version
ETA none Fixed in Version Product Version
  Target Version Product Build
Summary 0006648: TJvDateEdit CheckOnExit gives double error message
Description When you have 2 TJvDateEdit components on a form, the CheckOnExit displays the error message twice when you click on the other TJvDateEdit.

- Put 2 TJvDateEdit components on a form (JvDateEditA and JvDateEditB)
- JvDateEditA has CheckOnEdix set to true
- Enter an invalid date like 54.98.2465 in JvDateEditA
- Click on JvDateEditB
- Get 2x error message '54.98.2465 is not a valid date.'

This only happens when you CLICK on JvDateEditB. If you use the TAB KEY to switch to JvDateEditB then you get the error messsage only once.
Steps To Reproduce
Additional Information We use JEDI Visual Component Library 3.50
Tags No tags attached.
Attached Files zip file icon [^] (4,992 bytes) 2018-09-19 07:41

- Relationships

-  Notes
obones (administrator)
2018-08-30 14:15

Please provide the zipped sources of an application showing this.
TheBlackfish (reporter)
2018-09-19 07:42

I have attached a very simple example that shows the problem as explained.
mh (reporter)
2019-05-12 17:10

Some first analysis:

1. the provided test application doesn't work out of the box. The dpr needs to be modified like this, otherwise no form will be created:

program JvDateEditTestProject;

  JvDateEditTest in 'JvDateEditTest.pas' {Form1};

{$R *.res}

  Application.MainFormOnTaskbar := True;
  Application.CreateForm(TForm1, Form1);

2. There is a method CMExit in TJvCustomComboEdit which is triggered by a message CM_EXIT. It looks like this method is being triggered twice and there is the FInCMExit field which seems to be there to prevent double calls. Looks like the CM_EXIT message is not declared as completely processed. But why then doesn't this happen when using the keyboard instead of the mouse? There it only triggers this once.

- Issue History
Date Modified Username Field Change
2018-08-22 09:56 TheBlackfish New Issue
2018-08-30 14:15 obones Note Added: 0021573
2018-08-30 14:15 obones Status new => feedback
2018-09-19 07:41 TheBlackfish File Added:
2018-09-19 07:42 TheBlackfish Note Added: 0021576
2019-05-12 17:10 mh Note Added: 0021829

Mantis 1.1.6[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker