I am the original poster and have just joined perlmonks. Thanks so much for the advice. I have now gotten it working in the main program.
Just want to be sure I am correctly understanding what is going on. You can't actually pass a value from a subroutine to the main program using a button or other widget. Instead, you create a reference to the value of interest in the main program, send that reference to the subroutine and change the reference value in the subroutine. That changed value can then be accessed from the main program. Correct? | [reply] |
G'day jeri_rl,
Welcome to the monastery.
Just to clarify, if you have something like "... -command => sub { ... } ..." in your code, the "sub { ... }" part is the callback and it cannot return anything to the main program. However, code within the callback can return values. Here's another version of my original script that does just that:
#!/usr/bin/env perl
use strict;
use warnings;
use Tk;
my $tissue = 'plasma';
my $mw = MainWindow->new;
my $f1 = $mw->Frame()->pack;
$f1->Label(-textvariable => \$tissue)->pack;
$f1->Button(-text => 'Select Tissue', -command => sub { $tissue = sele
+ct_tissue() })->pack;
$f1->Button(-text => 'Quit', -command => sub { do_end($tissue) })->pac
+k;
MainLoop;
sub select_tissue {
# Tissue selection code here - assume 'muscle' selected
my $selected_tissue = 'muscle';
return $selected_tissue;
}
sub do_end {
my $tissue_to_print = shift;
# Print to STDOUT for demo purposes
print "$tissue_to_print\n";
exit;
}
If you run this code, you'll see it works identically to my original script.
Of course, this is a very simple GUI with very straightforward subroutines.
With more complex code, you can run into problems when passing values instead of references; on occasion, these can be hard to track down and rectifying them can involve reworking large parts of your code.
I'd recommend references over values in this scenario.
There's an added benefit of references being scalars, so you're potentially moving a lot less data around than you would with, say, @array_with_lots_of_elements or %complex_data_structure.
| [reply] [d/l] [select] |
With more complex code, you can run into problems when passing values instead of references; on occasion, these can be hard to track down and rectifying them can involve reworking large parts of your code. I'll bet half the problems come from all the closures :P
| [reply] |
sub MainLoop
{
unless ($inMainLoop)
{
local $inMainLoop = 1;
while (Tk::MainWindow->Count)
{
DoOneEvent(0);
}
}
}
You move the mouse, its an event (a bunch)
You click a button, its an event
Nothing happens for a few miliseconds, its an event
If you use Tk::Wizard then each page you add, each wizard step, is like a separate MainLoop, and then returning a value can be possible (you can write procedural code), see the examples | [reply] [d/l] |
Thanks. As you can see in the thread, I've got it working using references. However, looks like I should check out Tk::Wizard. Can you recommend an introduction or tutorial? I'm afraid I find the CPAN listings only useful if you already have an idea what you are doing.
| [reply] |