On Fri, Apr 21, 2017 at 12:21 AM, Kirk Brooks via 4D_Tech <
[email protected]> wrote:
> Tom,
> This is one place where the 'form controller' approach to managing form
> code works great. By having all the active objects on a form callback to a
> process method it's much easier to manage code used on a form than if it's
> residing in specific objects on the form. Granted you can export that code
> from each object but it's a real jumble when you do. By calling a
> controller method first it's much easier to see the context in the exported
> code.
>
Using a project method in place of a a form method/object scripts has a
couple of other advantages. If you pass in the event code, then you can:
* Create custom event codes ('redraw', 'close' or something more like a
message)
* Emulate form activity (useful for testing)
* Leverage your existing code with CALL FORM. Your CALL FORM call invokes
the form handler method and passes in whatever event or data is required.
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
