>Why do programmers play with pixel data in GWorlds, instead of using
>SetCPixel?
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", and you would do chunk expressions on graphics to edit the
data, that is "put 32767,32767,32767 into pixel 5 of grc 7". OC would do
the calculations needed depending on the pixel depth etc. But for starters
we should stick to the image-editing facilities HC contains.
>Good point. Wonder if domenu should be able to work on a menuitem number
>basis?
Not very good. Imagine some menu item ordering changes. e.g. between
platforms, items are in different locations, since e.g. while you use the
menu item "Quit" on the Mac, on Windows you click the current application's
close box to quit it. I think specific messages are better. They'll also
speed up processing, since if you trap domenu to handle undo, this domenu
handler is called for every menu choice, whereas a undoAction message is
only caught by those handlers who really concern themselves with undo.
It'll be faster, since not doing something is always faster than doing a
little fast.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
