On Sep 28, 2004, at 9:36 AM, Aaron Ballman wrote:
Would be nice to see it as "READ ONLY" in the debugger.
Doesn't make a difference in a lot of case -- simply accessing the
property can cause issues. A good example of this would be things
like FolderItem.GetSaveInfo (since it tries to resolve stuff) or
TCPSocket.Lookahead (which needs to do things if you're connected, and
if your not can fire errors). (which is why these are both methods
instead of properties).
Ah yes.
I suppose there will always be a certain class of item that will be
problematic in the debugger like these are.
There are other debugger dsplays that are like this.
That avoids the issue of changing it but enables the person doing the
debugging to be more
And if changing the values was the only problem, I would agree with
you. I think the read-only would be a great first step, but the
problem will still be there in one form or another.
Shortsightedness on my part to forget about items like you mentioned.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://www.realsoftware.com/listarchives/lists.html>
|