On Friday, March 22, 2002, at 01:57 AM, Dave Cragg wrote:
> on mouseUp
> put the imageData of image 1 into tData
> put 0 into tCount
> repeat for each char tChar in tData
> add 1 to tCount
> put charToNum(tChar) after tString
> if tCount = 4 then
> put tString & cr after tDisplayText
> put empty into tString
> put 0 into tCount
> else
> put comma after tString
> end if
> end repeat
> put tDisplayText into field 1
> end mouseUp
>
Here's mine:
on showImage
put "" into field "Image Data"
put the imageData of image "Test Image" into dat
repeat with n = 1 to length(dat)
put charToNum( char n of dat ) & ", " after field "Image Data"
if n mod 8 = 0 then put linefeed after field "Image Data"
end repeat
end showImage
Your's is much better because it accumulates in a variable while
mine accumulates in a field, which is slow slow slow. I'm learning.
> The binaryDecode and binaryEncode functions may give better
> options, but I tend to get a headache when trying to figure them
> out. :)
Oh. As a newbie I missed those. Thanks! I just mapped out some
mines and pitfalls in reading from processes on W2K; I'm ready for
anything.
To get this back on topic for improve...
Yes, a field makes a poor variable. And for persistence, custom
parameters and URLs are probably better choices.
But I think a field should obey some basic container rules. Until
then, a documented caveat that puts a boundary around the problem
areas would help the uninitiated.
Dar Scott
_______________________________________________
improve-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/improve-revolution
