I think that non-persistent IDE properties are the lesser of the two
evils. Otherwise you can easily lose track of your environment. But
the important thing is, custom properties and object properties ARE
persistent. Count on it.
Bob Sneidar
IT Manager
Logos Management
Calvary Chapel CM
On Feb 10, 2009, at 6:09 AM, [email protected] wrote:
Thank you, all.
It was just that, as Mark said, you have to already have at least
one bg to
set the editbg property at all. I thought I would set it and then do
some work.
Don't go "true" without it.
Incidentally, the property is not saved if one closes the stack and
then
reopens it; it defaults to "false" (saving the stack makes no
difference). So it
is not, in my thinking, much of a property, more like a temporary
tool.
This last disconcerted me; I could accept that I did not understand
the
limitation. I was upset that my idea of what a property was is now
useless. Are
most stack properties like that?
Newbies do a lot of whining.
I "have" Winkler, Kamins and DeVoto. And I have this list. I need
Danny
Goodman.
Craig Newman
**************
A Good Credit Score is 700 or Above. See yours in
just 2 easy steps!
(http://pr.atwola.com/promoclk/100000075x1218550342x1201216770/aol?redir=http://www.freecreditreport.com/pm/default.aspx
?sc=668072%26hmpgID
=62%26bcd=febemailfooterNO62)
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
