Bug 257343 - watch variable modification
Summary: watch variable modification
Status: RESOLVED DUPLICATE of bug 295929
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: 4.2.0
Assignee: kdevelop-bugs-null
URL:
Keywords:
: 289045 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-11-19 18:37 UTC by Chris Bruner
Modified: 2012-03-13 18:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Bruner 2010-11-19 18:37:58 UTC
Version:           unspecified (using KDE 4.5.3) 
OS:                Linux

When Looking at a variable in a watch window, or on a hint popup, it would be nice to be able to click on it,
and then modify it. 
Hitting Enter would save it. 
gdb set var x = n


Reproducible: Didn't try
Comment 1 Niko Sams 2010-11-19 19:28:11 UTC
How should that work with pretty printers? How do other IDEs that?
Comment 2 Chris Bruner 2010-11-19 20:07:42 UTC
Check out qtcreator for an example.
Double click on the variable, a text entry box appears with the old 
value. Edit the value and push enter.

On 11/19/2010 1:28 PM, Niko Sams wrote:
> https://bugs.kde.org/show_bug.cgi?id=257343
>
>
> Niko Sams<niko.sams@gmail.com>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |niko.sams@gmail.com
>
>
>
>
> --- Comment #1 from Niko Sams<niko sams gmail com>   2010-11-19 19:28:11 ---
> How should that work with pretty printers? How do other IDEs that?
>
Comment 3 leon pollak 2010-11-19 20:52:30 UTC
The old way it was done in kdevelop 3.5 is good enough too. I also vote for this feature.
Comment 4 Niko Sams 2011-12-30 18:21:40 UTC
*** Bug 289045 has been marked as a duplicate of this bug. ***
Comment 5 Niko Sams 2012-03-13 18:45:36 UTC
see also bug 72183

*** This bug has been marked as a duplicate of bug 295929 ***