On Nov 22, 2006, at 7:06 PM, Jeffrey Oleander wrote:
David Alger <email@hidden> wrote:
On 2006 Nov 21, at 14:41, Laurence Harris wrote:
This works for me. I know this will make some people's
eyes roll, but I much prefer the CW approach in which
the globals actually accessed in the current function
or scope are displayed in the list of variables in the
debugger window. Much more useful IMO.
Yeah, I liked and miss that. Frankly I can't stand
having to use a separate global variable viewer.
Maybe a 'Locally Used Globals' variable tree is in
I prefer both. I like to have a separate window for
globals, especially, e.g. when sorting out three globals
used by different predecessors to hold the same data. But
I also like the idea of simple ways to constrain such lists
to manageable proportions.
You can probably use expressions.
Yeah, but that would be a pain!
But it would also be nice to have a button in the globals
window to select just the globals referenced in the current
method/function... or even just the globals referenced by
that other function/method you were looking at a minute ago
together with the globals referenced in the current
method/function. (Toggling drives me nuts. I want to see
Maybe this would be just as nice, but having the globals referenced
by the function currently being viewed displayed in the variable list
in the debugger window would also be a time saver. For example, your
stepping through some code that modifies some global variables, every
time you want to see the results you either have to switch to a
different window or have the window somewhere else on the screen
where it will still be visible.
So, I think both would be nice. Why don't you file an enhancement
request? It will most likely never be implemented if nobody asks for it.
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden