Bug 42851 - Adding Goto Line feature to Chainsaw log panel
Summary: Adding Goto Line feature to Chainsaw log panel
Status: RESOLVED FIXED
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: chainsaw (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-10 21:15 UTC by Isuru Suriarachchi
Modified: 2008-07-03 12:54 UTC (History)
0 users


Attachments
Adding goto line feature to chainsaw (2.42 KB, patch)
2007-07-10 21:23 UTC, Isuru Suriarachchi 		Details | Diff
Adding goto line feature to chainsaw (2.42 KB, patch)
2007-07-10 21:25 UTC, Isuru Suriarachchi 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Isuru Suriarachchi 2007-07-10 21:15:23 UTC 
Currently, Chainsaw doesn't support the goto line feature in the log panel. It
will be useful for the users to find the exact log event when there are
thousands of log events coming in, rather than scrolling down. A key board short
shortcut should be used to implement this feature...
Comment 1 Isuru Suriarachchi 2007-07-10 21:23:49 UTC 
Created attachment 20487 [details]
Adding goto line feature to chainsaw

This patch contains the modifications made to LogUI in order to make Chainsaw
support goto line feature. I have used the CTRL+G as the key board short cut.
Comment 2 Isuru Suriarachchi 2007-07-10 21:25:54 UTC 
Created attachment 20488 [details]
Adding goto line feature to chainsaw

This patch contains the modifications made to LogUI in order to make Chainsaw
support goto line feature. I have used the CTRL+G as the key board short cut.
Comment 3 Paul Smith 2007-07-10 23:50:52 UTC 
The current patch has been applied, but I wouldn't mind adding the Action to the
'Current Tab' menu as well, it seems to make sense there I think as an action?
Comment 4 Thorbjørn Ravn Andersen 2008-07-03 12:45:00 UTC 
Is there any pending actions on this bug report?  I understand that the patch correcting the original issue has been applied, so it might be reasonable to change this from NEW to CLOSED/FIXED.