Thank you both for the help.

I believe this is a POE issue, as I've been perlapp-ing tk products for some time now.

In fact, you can actually get this to run if you use that trick I spoke about earlier. Instead of expecting poe_main_window to be there, simply set it yourself:

my $poe_main_window = MainWindow->new();

If you do this, the application will come up and run somewhat correctly. A better example of running somewhat correctly is in the pogram listed in my previous question, you'll see that everything works fine, but when the input stops, you can't scroll. I believe this has to do with the warning that Rocco puts in his documentation about not using MainWindow->new directly (that's my gut feeling, but I'm not sure).

My goal is to put together something similar to what is in my previous question, but I wanted to start at ground zero first, and figure out how to build a simple app with POE and Tk correctly.

I really appreciate the help on this, as I have to have something ready by the end of the month. If I can't get this to work with POE and Tk, I'll have to pull out the POE stuff (which I really don't want to do).

Thanks

-Craig

Update: Also, I believe it's true that just because perlapp includes a module, doesn't mean it is forced to be used. My understanding is that perlapp can include many modules, even ones that the application never uses (just excess baggage). It's just providing the environment for the perl script to run. If this is true, then it wouldn't matter that perlapp is including two mutually exclusive modules (POE::Loop::Select and POE::Loop::TkActiveState) and the application would just choose which one it wants to use.

My current gut feeling is that I just need to be including something that I'm not. I have no idea what that could be though...