This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Output Window Enhancements | ||
|---|---|---|---|
| Product: | cnd | Reporter: | aschwarz1309 <aschwarz1309> |
| Component: | Terminalemulator | Assignee: | issues@cnd <issues> |
| Status: | REOPENED --- | ||
| Severity: | normal | CC: | jhavlin |
| Priority: | P4 | Keywords: | UI |
| Version: | 7.2.1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
Almost all of the items work as you describe in the current development version (and it should work the same in 7.3). Only <Ctrl + Page Up/Down> not, because it's used for switching tabs. Do you really mean Output Window, not some other component, e.g. Terminal? Closing as WORKSFORME. Please reopen if you have any problems with Output Window in NetBeans 7.3 or newer. Thank you. Well, you must be right. It's probably the terminal window and not the output window. As to the use of ctl-PGUP/PGDN having another use and therefore being not available, if your focus is in an output/terminal doesn't that mean that keystrokes are captured in the handlers? And if they are captured in the handlers, doesn't that mean that the use of the ctl options can be made context sensitive? Or are you saying that keystroke use is unique because the Netbeans guidelines restrict usage to a single use? I think that I had this discussion with the terminal maintainer. He was opposed to using ctl-C for copy and ctl-V for paste and wanted to continue to use ctl-shift keystrokes for these operations. If I remember correctly his comment was that this was consistent with normal usage (I can't remember for what). My comment was that this viewpoint was inconsistent with Netbeans usage where ctl-PGUP/PGDN, ctl-A, etc. are used in the manner suggested. Alas, I appear have confused OUTPUT with TERMINAL and you were assigned the odious task of responding to me. But thanks. I appreciate all that you and the Netbeans 'crew' do to make it easier to do the impossible. If you can convince the TERMINAL maintainer to change his perspective it would be most appreciated. art (In reply to aschwarz1309 from comment #2) > As to the use of ctl-PGUP/PGDN having another use and therefore being not > available, if your focus is in an output/terminal doesn't that mean that > keystrokes are captured in the handlers? Yes, it does. > And if they are captured in the > handlers, doesn't that mean that the use of the ctl options can be made > context sensitive? Or are you saying that keystroke use is unique because > the Netbeans guidelines restrict usage to a single use? We could override the keystroke in the Output Window, but I think it's better if the keystrokes are consistent with editor and the rest of the IDE. Anyway, you can still use Ctrl-HOME and Ctrl-END. > I think that I had this discussion with the terminal maintainer. He was > opposed to using ctl-C for copy and ctl-V for paste and wanted to continue > to use ctl-shift keystrokes for these operations. If I remember correctly > his comment was that this was consistent with normal usage (I can't remember > for what). Probably the reason was using Ctrl-C for SIGINT. > My comment was that this viewpoint was inconsistent with Netbeans > usage where ctl-PGUP/PGDN, ctl-A, etc. are used in the manner suggested. I don't work with Terminal component too often, but I believe that if its maintainers use nonstandard shortcuts, they have good reasons for that. > Alas, I appear have confused OUTPUT with TERMINAL and you were assigned the > odious task of responding to me. No problem at all :-) > But thanks. I appreciate all that you and > the Netbeans 'crew' do to make it easier to do the impossible. Thank you, too, for spending your time reporting bugs to make the IDE better. > If you can convince the TERMINAL maintainer to change his perspective it > would be most appreciated. I'm reopening and reassigning the bug. |
Product Version = NetBeans IDE 7.2.1 (Build 201210100934) Operating System = Windows 7 version 6.1 running on x86 Java; VM; Vendor = 1.7.0_03 Runtime = Java HotSpot(TM) Client VM 22.1-b02 1: a. Placing the cursor to the left of the first character in the output window, then b. Pressing and holding the shift key, then c. Using the vertical scroll bar to go the end of the output window, then (optional step) d, Placing the cursor anywhere on the last line has no effect. What I would have expected is that the entire output window would be highlighted. However, repeating step 1 a and 1 b and then moving the cursor (causing any portion of the first line to be highlighted) and doing step 1 c (optional) and 1 d has the desired effect. That is, any portion of the output window can be highlighted if the cursor is positioned at the start point, the shift key is depressed, and the cursor is moved on the same line, and then the region to be highlighted is selected. 2. Ctl-A would be nice to allow highlighting of the entire window. 3. Ctl-C would be nice to copy a highlighted region (and consistent with the editor). 4. Ctl-PGUP or Ctl-HOME would be nice to go to the top of the output window (left of the first column on the first line of output). 5. Ctl-PGDN or Ctl-END would be nice to go to the end of the output window (right of the last column on the last line of output). 6. HOME would be nice to go to the left of the first column on the current line. 7. END would be nice to go to the right of the last column on the current line. In the end, make the keys and actions similar to that of the editor in the source window.