|
Revision 1171, 458 bytes
(checked in by paul, 3 years ago)
|
Fixed dGrid so that the test loads correctly in test.py. There is still
a lot of refactoring to be done in dGrid to work it in to a robust Dabo
control, but this was the minimum required to get the test to instantiate.
Fixed the test to show the actual traceback when there's a problem
instantiating a control.
Changed the dGauge test to be more Dabonic.
|
| Line | |
|---|
| 1 |
See: |
|---|
| 2 |
|
|---|
| 3 |
http://dabodev.com/wiki/ReleaseRoadmap |
|---|
| 4 |
http://dabodev.com/wiki/DeveloperRoadmap |
|---|
| 5 |
|
|---|
| 6 |
|
|---|
| 7 |
##pkm: Here are some open items: |
|---|
| 8 |
|
|---|
| 9 |
+ datanav: |
|---|
| 10 |
|
|---|
| 11 |
+ editing new records results in those edits being lost. This |
|---|
| 12 |
could be a datanav issue, but may be a base dCursor issue. |
|---|
| 13 |
|
|---|
| 14 |
+ date/datetime fields can't be edited: None will get sent back |
|---|
| 15 |
to the database, resulting in a NULL value for the field. Again, |
|---|
| 16 |
at this point we don't know if this is datanav or dCursor. |
|---|
