At 3:28 PM +0100 on 11/25/99, M. Uli Kusterer wrote:
Anthony,
I think adding direct access to pixel values this way is a rather big
addition to OC. If we really wanted it, I'd say we extend graphic objects
to support this natively. That is, there are properties like "the depth of
pixel map 5",
At 7:10 AM +0100 on 11/25/99, M. Uli Kusterer wrote:
And then try and teach scripters about the format of pixmaps, handle
conversions between fromats, platforms, color sets, bit depths, check to
make sure pixmaps are valid before use, etc., all quickly and transparently
to the scripter user.
And then try and teach scripters about the format of pixmaps, handle
conversions between fromats, platforms, color sets, bit depths, check to
make sure pixmaps are valid before use, etc., all quickly and transparently
to the scripter user.
Anthony,
why should users want to edit the
At 11:07 PM +0100 on 11/22/99, M. Uli Kusterer wrote:
But it'd be hard to convert everything to text form -- e.g., how do you
convert a 24-bit pixmap to text?
Anthony,
not a problem. Since our variables have no problem with NULL characters,
we'd just need something like the pictureData
But it'd be hard to convert everything to text form -- e.g., how do you
convert a 24-bit pixmap to text?
Anthony,
not a problem. Since our variables have no problem with NULL characters,
we'd just need something like the pictureData property (which returns a
long stream of bytes representing
Clip: Libundo is a simple, easy-to-use lib which
manages recording and playback of undo/redo info
for app developers.
Alain: Infinite undo/redo would be a wonderful feature
for OpenKard. It could also make OpenKard recordable.
Uli: I think we can do undo the way SuperCard does it,
that is,
