[kcachegrind] [Bug 388740] Ordering by timestamp instead of core number

https://bugs.kde.org/show_bug.cgi?id=388740 --- Comment #5 from Josef Weidendorfer --- > hmm... then maybe there could be a hierarchy for the ordering : first > creation time, then PID ? This should be done automatically by the Qt widget... Adding the column should be easy, by looking at the s

[kcachegrind] [Bug 388740] Ordering by timestamp instead of core number

https://bugs.kde.org/show_bug.cgi?id=388740 --- Comment #4 from Jean-Michaël Celerier --- (note: I'm entirely willing to implement the feature myself if I'm pointed out roughly where this should happen in the code) -- You are receiving this mail because: You are watching all bug changes.

[kcachegrind] [Bug 388740] Ordering by timestamp instead of core number

https://bugs.kde.org/show_bug.cgi?id=388740 --- Comment #3 from Jean-Michaël Celerier --- hi! yes, both the workaround and your suggestion look fine (of course, not having to remember to add some argument to the valgrind command line would be better !). > For multithreaded code, this time will

[kcachegrind] [Bug 388740] Ordering by timestamp instead of core number

https://bugs.kde.org/show_bug.cgi?id=388740 --- Comment #2 from Josef Weidendorfer --- Interesting suggestion. For multithreaded code, this time will be the same for multiple files. Is this about the ordering in the "parts overview"? Does it help to add a column "Creation time" or similar, and y

[kcachegrind] [Bug 388740] Ordering by timestamp instead of core number

https://bugs.kde.org/show_bug.cgi?id=388740 Julian Seward changed: What|Removed |Added CC||jsew...@acm.org --- Comment #1 from Julian Sewa