[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 140594] kdevelop fails to evaluate local variables
From: kbugger <kbugger () piments ! com>
Date: 2007-01-29 19:32:29
Message-ID: 20070129193229.16530.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=140594
kbugger piments com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|fails to correctly evaluate |kdevelop fails to evaluate
|local variables |local variables
------- Additional Comments From kbugger piments com 2007-01-29 20:32 -------
Ah! I have realised since posting what is happening. My bad, I added it as an eval \
not a watch.
Maybe the header "Recent" could be made more explicit, recent what? In the context of \
dynamically updated locals and watches nothing suggests that these are either fixed \
and no longer relate the varialbes they include.
Perhaps "static evaluations" would be a clearer indication of what is shown.
since I've got a line open could I suggest two other enhancements here?
Context menu for a watch could include "modify watch" where the text would be copied \
to text entry for modification. (especially useful since the watch can not be \
selected as text for copy, only highlighted).
similarly the expressions listed could have an context entry "refresh" that would \
cause them to be re-evaluated.
Both pretty trivial to code and nice added functionality.
regards.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic