I've done some thinking about how you can avoid the locking
up of the gui while the new messages are retrieved. That is,
if you don't want to attempt some fork()ing and force everyone
to upgrade to perl 5.6.
My solution is to separate the gui from the calls to retrieve
the messages and have the messages stored in a file. Then
make it so the program can be started with an argument, to
tell it which mode it should start up in.
So, you would launch the program in gui mode first, then it
would use the Win32::Process module to launch a second copy
of itself in retrieval (non-gui) mode. So then you have 2
processes running independantly of each other, communicating
via disk files.
It's a kludge, but it totally gets rid of the problem with
the frozen gui. Unfortunately it requires nearly a complete
rewrite of the code.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||