[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    [Bug 68610] Enhance problem reporter for more advanced analysis
From:       F Fracassi <f.fracassi () gmx ! net>
Date:       2003-11-20 7:02:13
[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=68610     




------- Additional Comments From f.fracassi@gmx.net  2003-11-20 08:02 -------
Full Ack. Three More Points:
1) Simple Wish:
 	- support the doxygen commands @ISSUE, @BUG like the @TODO.
	- make it work on the counterparts \ISSUE \BUG \TODO
2) Fix Makro usage:
	I sometimes use makros for komplex Debug output (Debug images) like this: 

#define VDBG(s) s

And then latter invoke it:

VDBG(
  Image dbgimg();
  ...
  dbgimg.save();
);

which is perfectly legal c++, but the Problems Reporter marks each of these \
invokations as wrong, thus cluttering the view.


3) Make it possible to rank the problems: 
   for example throug RMB click on a problem a small menu pops up which lets you give \
the problem a priority from 1 to 5 (3?, variable?) and perhaps an option for "hide \
this Problem" The problems should then be sorted by their ranks first.

_______________________________________________
Kdevelop-devel mailing list
Kdevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel


[prev in list] [next in list] [prev in thread] [next in thread]