Program Testing and Persistent Properties

[Troy Rollins]

On Aug 7, 2004, at 2:32 PM, Bob Warren wrote:

> I documented this attempt at testing the project and recorded my 
> confusions
> in an article at http://www.howsoft.com/runrev/article.htm .
> If anyone has the patience to read through this illustrated story, 
> would
> they please enlighten me as to the "higher purpose" of "persistent
> properties" when test-running a Rev project! (The meaning or 
> "persistent
> properties" is abundantly clear in the article.)

The "higher purpose" is that it makes it extremely easy to save a users 
input values, drawings, data, etc. simply by saving the stack. It is 
basically a shifting of how you think about programming. The concept 
that it shouldn't be hard to save a user's input and data is one of the 
driving forces behind this.

To correct this, all Bob needed to do was place scripts like -

on openCard
	put EMPTY into Field "Field 1"
end openCard

This would clear the field each time the card was opened.
--
Troy
RPSystems, Ltd.
http://www.rpsystems.net