> > If it is dynamic, your run-mode maybe looks like this:
> >
> > sub update_record_and_return {
> > my $self = shift;
> >
> > $self->SaveData();
> >
> > return $self->dynamically_choose_next_screen();
> > }
I'm unclear on what is wrong with the suggestion I made the last time this
issue was raised:
write a subclass of CGI::App that adds the
dynamically_choose_next_screen() routine above, which uses a variable set
in setup() via run_mode() and start_mode()-like routines. Make all of
your apps subclasses of this.
Granted, you'd have to manually put said return call in your non-outputing
modes, but that seems minor. If you disagree, you can overload run() to
call run_mode(), then output the results of output_mode(), though that
would remove the easy upgrade path when CGI::App gets upgraded.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
