Thanks Aristotle... I'll chase it up there as well.. I should have added that I tried copying all the Gtk2 stuff from the 5.8.3 distro to my 5.8.4 with the same non-result. Is it in fact OK to just copy components into my Perl "database", or does everything have to be properly installed with makefile etc ?
Another question.. is the Perl "database" (i.e. /usr/local/ActivePerl58) self-contained ? I.e. is all the info relating to what perl modules etc I have installed contained within that directory, or does Linux keep info about perl libraries somewhetre else as well ?

Also, my question is about perl gui debugging in general... how do the experts debug X display scripts ? I'm an amateur programmer (these days) doing community stuff, so I don't have access to work colleagues.
thanks.. Rod


In reply to Re^2: Perl-Gtk2 debugging help needed by rbutcher
in thread Perl-Gtk2 debugging help needed by rbutcher

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.