Guess I didn't step away enough to have it make sense to anyone else....
That said, here's some code:
sub cgiapp_prerun {
my $self = shift;
my $dbh = $self->{DBH} = $self->param('DBH');
### let's check for storage;
my $previousClass = $self->query->param('this');
my $className = "DataClasses::${previousClass}";
if ( $className->SUPER::can( 'new' )
and $className->SUPER::can( 'store') ) {
my $object = $className->new(
DBH => $dbh, REQUEST => $request );
## the needStorage method allows us to
## have multiple "screens" using the same class
## where not all of them store in the DB
$object->store() if $object->needStorage();
}
}
}
and the store() method ...
sub store {
my ( $self, %params )_ = @_;
### if insert ...
$self->query->param( -name => 'whatever', -value => '123');
$self->param( 'whatever', '123' );
return 1;
}
both methods of stashing the value until the runmode is executed failed. as i've understood the calling stack:
CGI::App->new() -> prerun -> setup -> "runmode" -> teardown
so i don't see how something set in one mode wouldn't carry into another, because it's the same "run cycle".
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.