Ismailtaktak / freemedforms

Automatically exported from code.google.com/p/freemedforms
Other
0 stars 0 forks source link

CalendarItemEditor - after patient removal, no other patient can be added. #197

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
* add a new calendar item with a double click, the editor dialog opens.
enter the patient search line edit and enter a char. the popup opens, select a 
patient, the patient gets added.
* add another patient.
* now delete one patient with the funky X button right

-> now you can NOT add another patient to the list.

Original issue reported on code.google.com by christian.a.reiter@gmail.com on 19 Oct 2012 at 10:29

GoogleCodeExporter commented 9 years ago
This bug is reproducible like this too:
- create appointement
- add one patient
- click anywhere in the patient view
- bug...

Original comment by eric.mae...@gmail.com on 19 Oct 2012 at 7:52

GoogleCodeExporter commented 9 years ago
I didnt find the bug but added a work around patch

Original comment by eric.mae...@gmail.com on 19 Oct 2012 at 8:06

GoogleCodeExporter commented 9 years ago
Hm, this bug is gone, but not comepletely.
I have the random users in my DB.
now when I press "s" and add the first Patient in the "s" list named "SDF Gh 
HG", a second patient named "ASCENSEUS HAWAS ASPIRANTES" which is the FIRST 
PATIENT IN THE LIST, gets added too.
if I select the second "s" patient, the second "a" patient gets added.
So with one click I have two patients added.
This only works with some patients; some are added alone just as intended.

What puzzles me:
in the focusInEvent you connect the signal to the slot, but never disconnect 
it? So each time you enter the lineEdit, a new connection is established?
shouldn't it disconnect on focusOut?

Original comment by christian.a.reiter@gmail.com on 19 Oct 2012 at 8:59

GoogleCodeExporter commented 9 years ago

Original comment by christian.a.reiter@gmail.com on 19 Oct 2012 at 8:59

GoogleCodeExporter commented 9 years ago
Oh, yes, this was the problem. I fixed it with Qt::UniqueConnection (whow, 
again something learned for myself...)

Original comment by christian.a.reiter@gmail.com on 19 Oct 2012 at 9:14