Hi,
Since we upgraded to ULC 6.1 from ULC 6.0.4, we have noticed some strange behaviour in a text field and would like to know if it is as a result of some optimization added in ULC 6.1.
What happens is this:
We have a pane that starts out with a single row with the following data:
(checkbox) TextField DateField
There are two buttons at the bottom. One will add a new row and the other will delete the rows that are checked off.
The date field is just a text field with a data type of ULCDateDataType in a particular date format. If you input an invalid date format or any non-sensical value - like "48fk49tk", for example, when you tab out of the field the value goes blank. This is the same behaviour as the previous version of ULC. However, when you click back into the field to enter a new value, the old non-sensical value comes back. As far as I can tell, this is new behaviour for ULC 6.1. If there is a way to stop this from happening, I believe we can fix the problem. However, there is more to it.
Now after you've entered the non-sensical value into the date field, if you add another row, that works just fine. I would then modify the value in the plain text field to make sure that we can identify the difference between the two rows. The table should then look like this:
(checkbox) (empty text field) (date field that looks empty, but when you click into it has the value "48fk49tk" displaying)
(checkbox) "Row Number 2" (date field that actually is empty)
Next I would delete the first row (the one with the non-sensical value in the date field). The results appear as expected - the empty text field is gone and the "Row Number 2" row is still there. However when you click into the date field in the remaining row, the non-sensical value from the original first row is there:
(checkbox) "Row Number 2" (date field that looks empty, but when you click into it has the value "48fk49tk" displaying)
We have made sure that we are actually attempting to put in the correct date field, but the only thing that we can think is happening is that ULC is seeing that we are trying to replace an empty date field with an empty date field, so it is actually leaving the original date field (with its non-sensical value) in place. Perhaps ULC always did this and the only change is that now the date field is keeping the non-sensical value? Or perhaps it always did keep the non-sensical value and something else has changed. Any clues as to what is going on here would help us out greatly. We would especially like to know how to get that non-sensical value cleared out of our date field completely.
Thanks.
Elizabeth Kliman, B.Sc., SCJP
Developer / Développeur
Information Technology / Technologie de l'information
Farm Credit Canada / Financement agricole Canada
1800 Hamilton Street, P.O. Box 4320
1800, rue Hamilton, C.P. 4320
Regina SK S4P 4L3
Tel/Tél. : (306) 780-3382 Fax/Télec. : (306) 780-5655
E-mail/Courriel : [EMAIL PROTECTED]
Agriculture. It's all we do. L'agriculture... notre raison d'être.
This message may contain information that is privileged, protected, confidential or subject to copyright. Using, disclosing, copying or distributing such information by anyone other than the intended recipient is strictly prohibited. If you’ve received this message in error, please delete it and notify me immediately.
Le présent courriel contient des renseignements de nature privilégiée, protégée, confidentielle ou assujettie à des droits d’auteur. Toute utilisation, communication, reproduction ou distribution de l’information contenue dans ce courriel par toute personne autre que le destinataire visé est strictement interdite. Si vous avez reçu ce courriel par erreur, veuillez le supprimer et m’en informer immédiatement.
