Remembering variable state

[Ramon Zarazua]

>Folks,
>
>I have a user-level design question for local variables view.
>
>Say, at some moment in time, you looked in frame 2 of thread 1
>and saw variable 'v', which is of class type. You have expanded
>it, and changed the format of second child to hex.
>
>Some time later, evil fate has you looking at thread 5, frame 4.
>You have a variable in that frame, which is either also called 'v',
>or has the same type as 'v', or both. Now -- should that variable
>be also shown as expanded, and should its second child have hex
>format?
I think the best way to go would be to actually let the user decide. It makes 
sense to me, to have a marker (checkbox probably) that when activated, it 
signals that the view for that type should be remembered(I don't really see 
use for variables of the same name though).
>
>How does the answer changes if we're looking at the same thread, or
>the same frame, or if the frame is innermost in all cases?
If it is the same frame, it makes sense to me that the variable would be 
displayed the same way as last time.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090613/d29b7113/attachment.sig>