Tk killing binary?

Cybercosis has asked for the wisdom of the Perl Monks concerning the following question:

I have a small app that requires me to get some data from a Tk Entry widget. I have no problem if the data is just text, but if it's binary, it somehow gets munged in transit. Is there any way to fix this?

~Cybercosis

nemo accipere quod non merere

Comment on Tk killing binary?

Replies are listed 'Best First'.
Re: Tk killing binary? by physi (Friar) on Aug 04, 2001 at 11:00 UTC
some code would be helpful ... Maybe you could use `pack` ?? `----------------------------------- --the good, the bad and the physi-- -----------------------------------` [download]	[reply] [d/l] [select]
Re: Tk killing binary? by kschwab (Vicar) on Aug 05, 2001 at 18:55 UTC
I suspect that the X11 cut buffer is what's munging your data. You could test this by not using it... `# create a string with binary data my $binary="string\000with\000nulls"; # empty out the entry widget $entrywidget->delete(0,"end"); # insert the data $entrywidget->insert(0,$binary); # pull back the data with get and compare to the # original data my $gotback=$entrywidget->get(); if ($binary ne $gotback) { print "hmm...buggy?\n"; # throw in some hexdumps here ? }` [download] If you can't solve the problem with binary data, perhaps you could have the user input the binary data with some sort of encoding (Base64, urlencoded,etc) ?	[reply] [d/l]


"be consistent"
	PerlMonks