Project

General

Profile

Feature #6473

better approach for default event behavior

Added by Greg Shah almost 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
version:

History

#1 Updated by Greg Shah almost 2 years ago

As Marian notes in #6394-10, we often see some problems in handling default behavior for an event:

  • Sometimes the default behavior is not implemented at all in FWD.
  • Sometimes it executes (or doesn't execute) differently than the 4GL.

We need to test default event behavior (and user-defined triggers) for the full range of events and widgets. Then we should implement a more consistent approach to default event behavior.

Marian suggests having a registered default event trigger that is not user defined. That would be a consistent approach and also has the appeal of being clean and easy to understand. It does have some drawbacks:

  • These triggers would not run on the server, so the firing of them would still need to be different.
  • We would not want them to be included in the EventList since it would add hundreds of additional triggers and that is costly since the code there is performance sensitive.

Whatever we decide, it needs to be clean and consistent.

Also available in: Atom PDF