Login
Templates, Tools and Utilities
for Clarion Developers
Templates, Tools and Utilities
|
||
|
|
|
Icetips Article
Back to article list
Search Articles
Add Comment
Printer friendly
Direct link
Par2: Window Manager -- Sequence of Events 1998-07-27 -- Jon Waterhouse With a little digging in the ABWINDOW.CLW file I came up with the
following sequence of events. These are WindowManager methods.
In TakeAccepted if the control is the control that has been designated
the OkControl, the PostCompleted method is called.
PostCompleted calls the NonStop acceptance loop which posts
Event:Completed when it is finished (or posts event completed
immediately for deletes).
The TakeWindowEvent traps the EVENT:Completed and calls the
TakeCompleted method.
The TakeCompleted method saves the history buffer, then does the real
insert/change delete based on the value of ThisWindow.Request.
So maybe you should put your stuff at the end of the TakeCompleted
WindowManger method?
---------------------
Douglas Johnson adds:
After EVENT:Completed is posted the following happens:
WindowManager.TakeCompleted -> (calls)
RelationManager.Update ->
FileManager.UpdateServer ->
FileManager.ValidateRecord ->
FileManager.ValidateFields ->
FileManager.ValidateField
This sequence permits DCT validation for all fields, some of which
duplicate calls already made during PROP:AcceptAll = True and
others which handle generated or embedded code completely
unknown by a particular form.
Depending upon the desired action when this validation code
encounters an error, it may be difficult to gracelfully reselect the
offending entry field and return to updating the form.
** The above sequence may be different for client-server/SQL
files where validation is done by the server.
Today is April 19, 2024, 7:53 am This article has been viewed 35113 times.
|
|