So, I tried a few things the first was to see if the data was coming across the socket. Here's my simple script: 
#!/usr/bin/perl

use IO::Socket; 
my $sock = new IO::Socket::INET ( 
    LocalHost => 'localhost', 
    LocalPort => '7070', 
    Proto => 'tcp', 
    Listen => 1, 
    Reuse => 1, 
); die "Could not create socket: $!\n" unless $sock;


my $new_sock = $sock->accept(); 
while(<$new_sock>) { 
    print $_;  
 } 
close($sock);
__END__

[download]
And it works, data comes across the socket, and shows up in the command window. I do think the problem is in the fileevent. But, I can do the read like I did in my small script, but how do I pass what is read to TK and then use it within its subroutines to build the graph?

In reply to Re^5: Tk Realtime data aquisition by jaschwartz
in thread Tk Realtime data aquisition by zentara

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.