Below is the issue found in the actual development of Delphi, I hope to communicate with everyone.
1, TDATETIMEPICKER error
The TDATETIMEPICKER control has many errors when reading and writing, mainly the date cannot be refreshed in time.
Just give an example:
Create a new form, then add a TDATETIMEPICKER control, just place a floating button such as TSPEEDButton or TtoolButton, I believe there are many ways to use!
Add a simple code to the Click event of the floating button:
ShowMessage (Formator-mm-DD ', DateTimePicker1.date);
At this point, you modify the time value of TDATETIMEPICKER, then activate the Click event of the floating button, you will find the date that is reflected in the TDATETIMEPICKER is not a TDATETIMEPICKER true date! Try a few times, you will find the problem more serious!
I believe that Borland's people should measure this error, but there is no repair!
It seems that there is no date DB control!
2, TDBGRID error
If you read and write data directly through TDBGRID, you will find the problem very fatal!
Just give an example:
Create a new form, then add a TDBGRID, add the appropriate data association and activate the data source, just place a floating button, I believe there is more useful!
Add a simple code to the Click event of the floating button:
ShowMessage (AdoQuery1.fields.fields [0] .sstring);
Then run!
First select a data in TDBGRID (one item has been selected by default), then scroll the roller toll data of the mouse, just the usual internet is scrolling the web page or simmer the browsing in the Excel data area, then click in TDBGRID. You will find that two data is actually controlled in TDBGRID, and there may be multiple!
continue!
If you keep rushing to the cursor in tdbgrid under the cursor of the mouse and then click, then activate the Click event of the floating button, you will find that the actual current data in the data source in the TDBGRID is inconsistent with the actual current data in the data source!
I believe this situation in practical applications: I obviously choose this data, but why is this data?
3, tquickrep error
TQUickRep has traveled to use simple and flexible (of course, by adding code), of course, her defects are equally famous, and this is certainly not complete Delphi problem.
Just give an example:
The system main window is the FormStyle is the fsmdiForm type, and the various forms in the system use a mode form (ShowModal), which is a very common application.
In the actual system main window is often maximized (WindowState = WSMaximized), if you preview the report in the mode form:
Quickrep1.preview;
If you minimize the report preview window, you will find that you can't close any windows at all! Unless it is forcibly turned off by Alt Ctrl delete!
Fortunately, Qusoft has discovered this problem, in the professional version (currently version 3.6.2) solution is actually the preview window default is a normal window instead of the standard version to maximize the form!
4, Ide development tool
I believe that at least 99% is developed directly through the IDE tools provided by Delphi, in practical applications, in order to reduce the size of the EXE file (mainly due to the relatively large third-party control), it is often by canceling part of the VCL connection library ( For example, non-delphi itself * .bpl) is completed, and now I have almost impossible to add it in Delphi, or don't add it! Regardless of how you set in [Build With Runtime Packages], it seems that the IDE tool only identifies the [-lu] parameter in the check or cfg file, regardless of others!
Note: There is still no confirmation of this or other issues, but it is generally considered to be an IDE tool.
Hank
Starfarm@263.net
2002.12.12
