some more minor bugs noticed in 0.5.3rc2

[shiraz]

1. when in a group, widget type for calendar widgets shows time even if SQL field is date (not datetime) or even if widget:showsTime=0 is set in fields.ini

2. delete trigger fails (does not trigger) when it is sequentially the first method of 3 methods (ie. after afterInsert and afterUpdate), but works when it is the first function in the delegate class.

3. if a field is set to autocomplete in fields.ini, using a valuelist based on a sql table, and if the value in that field is something other than a value from that table (ie. was externally populated), then the field shows as blank in list view, even though it shows correctly in details view

[Aoirthoir]

Mr. Steve,

Are issues 1 and 2 resolved?

Issue 3 I think is something different, since the valuelist will only allow what is in the tables in that case...or what is in the valuelist if valuelists.ini is using value = description.

Not sure though if it should automatically consider the following:

[valuelistname]
value = current value
sql = ?
or
values = values

...

Meaning..I can currently set mine like this:
[IDs]
16775 = No Choice
__sql__ = "Select bla, bla from bla bla...etc"

What this gives me is..a no choice option in addition to the options from the table. I usually set it to the highest value allowable for the int/mediumint etc field. So the first value list would be an example of this, only displaying the current value even if it is not in the sql or valuelist list. This way folks will be able to view the original data in the field if it was imported from someplace else...So there might need to be another field to allow DF to either force the select to the valuelist, or also allow for displaying original data.