[oopic] The future of ooPIC

It appears that the recent announcement to discontinue the 8-bit
products has met with,... well catoragize it as you may.

For those of you who are taking the news hard, let me offer an
explanation.

It is a simple matter of economics.

The 8-bit products do not sell.
The 16-bit products do.

On a second subject,

The oEvent object appears to be causing a great deal of distress.
Let me offer an explanation for that as well.

The oEvent object is a method of running interpreted code in response
to an event. However, the user community has historically tried to
use it in ways that it was never designed for nor *advertised* to
do. Consequently, it has been the source of problems for both Savage
Innovations and the user community.

Since all documentation on the actual workings of the oEvent object
are also historically ignored, then my solution to this issue should
have been to remove the oEvent object entirely in the last release of
the software. I didn't. In retrospect I should have.

There is now a bug in the compiler that affects the oEvent object. I
did say that this bug would be fixed in the next release of the
compiler and it will. But allow me to make a comment: This will not
fix the fact that the user community tries to use this object in ways
that it does not and will not work.

Scott Savage

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)

<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/