Still, using binary data seems to be faster:
Definitely worth having. I look forward to it filtering it's way through the chain into a an AS distribution.
Maybe it's somehow possible to prevent this, for example by using a special reference or magics for the value of -data, which wouldn't be upgraded by Tcl_GetString calls.
I'm not sure what you mean by a "special reference"?
To me, it doesn't make sense to pass such large volumes of data (as images tend to be) by value. Especially if the receiver is going to have to make another copy when it gets it. If the call was designed to take a reference, then it could read the data directly from the callers space as it does whatever (the first) conversion is needed.
That needn't even change the current interface. It just needs to test if it's been given a reference and do the current thing if not.
But I think I have first to learn how the Perl/Tk internals work at all...
Out of interest, how big are the sources for Perl/Tk? Anything beyond a few 10s of MB, and it gets silly trying to get an up to date copy via a 40kb/s connection. It changes faster than I can download it.
In reply to Re^7: Tk:Photo -data with binary data?
by BrowserUk
in thread Tk:Photo -data with binary data?
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |