[wxperl-users] Wx::Perl::SplashFast

[Bradley K. E. <bke...@ex...>]

I am not sure if this is actually a bug, but here is something that I have
observed.

If I specify a _short_ timeout for the splash screen then my application
dies with error:

Terminating on signal SIGALRM(14)

If I increase the timeout enough then my app loads with no problems. The
amount I have to increase the timeout seems to depend on the speed of the
computer, with my home P-III 667 needing a larger timout than my work Athlon
XP 1800+.

I assume that the problem is the timeout is not long enough for my app
module and all related modules to load, and the signal to terminate the
splash screen instead terminates the application. Just a wild guess though.

I have not yet tried using Wx::SplashScreen to see if the same thing occurs
using it directly.

Here is the code using SplashFast (on ActiveState build 805; Wx 0.13 beta
from ppd):


#!/usr/bin/perl -w

# protect us from ourselves
use strict;
use warnings;
use diagnostics;

BEGIN
{
  # we show a splash screen to amuse users while the app loads
  # we put this in a BEGIN block to ensure it loads and runs right away
  # import the modules we need
  use Wx::Perl::SplashFast;
  Wx::Perl::SplashFast->new(
                             "./img/logo.jpg", # splash screen image
                             2000              # num of ms to show splash
                           );
}

# import the modules we need
use ExcelKitchens;

# create an instance of our app and start it up
ExcelKitchens->new()->MainLoop();


Am I using SplashFast incorrectly, or is this behaviour to be expected?

Brad