[Lazarus] Watches/Local variables/Registers [Re: IDE UI consolidation (was: Re: lfm as pascal)]

[Alexander Klenin]

On Thu, May 7, 2009 at 20:55, Martin Friebe <lazarus at mfriebe.de> wrote:
>>>> They should be merged together in a single list with appropriate
>>>> filtering capabilities.
>>>>
> ....
> another thing with combining them, is that the amount of Locals keeps
> changing (watches just display unavailable).
>
> This means that (unless locals are last in the list), everything keeps
> changing position, and you have to adjust where to look for it.

Agree, thy should be the last.

> (OT: Would be a great feature to bind watches to a stackframe, and have
> them changing automatically...)
+1

>> What kind of long values do you watch?
>>
>>
> Mainly structures/records/classes...
> Of course that would be better solved, by having each member on a line
> of it's own.
Agree.

> You also have to find a way how to deal with different properties that
> watches can have (not yet, but in future: mem-dump, hex, dec, ... hust
> see the property window). In princible they can be applied to locals, as
> long as you can find a way to match them, each time locals had been
> updated. Because if you change stack frame you may have a local with the
> same name, but it is a different variable. So how to you bind those
> properties to a local value?

Well, since the display format is per-value, this issue is
totally orthogonal to the window consolidation. In fact, if display format
is going to be controlled by e.g. context menu, then said consolidation
might save some duplicated code.

> Not sure if those props make sense for registers....

Well, dec/hex definitely do. I actually looked at registers at the first time
during this discussion and was surprised that some values are in decimal

-- 
Alexander S. Klenin