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.

Bug 146196 - Problem with code movement and guarded blocks
Summary: Problem with code movement and guarded blocks
Status: RESOLVED WONTFIX
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: PC All
: P4 blocker (vote)
Assignee: issues@editor
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-04 14:55 UTC by Petr Dvorak
Modified: 2009-11-02 10:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Petr Dvorak 2008-09-04 14:55:16 UTC 
Product Version: NetBeans IDE Dev (Build 200809021401)
Java: 1.6.0_10; Java HotSpot(TM) Client VM 11.0-b15
System: Windows XP version 5.1 running on x86; Cp1250; cs_CZ (nb)

Moving code (Shift+Alt+Up/Down) behaves strangely in interaction with guarded blocks

0. Create Java Application with a JFrame form

1. Select some guarded text (event handler) and press Shift+Alt+Up (move selection up)
-> nothing happens

2. Select some guarded text and press Shift+Alt+Down (move selection down)
-> selection is copied bellow the original selected text in GB

3. Select some block of normal code that is above some guarded section (main method + Variables declarations) and press
Shift+Alt+Down several times
-> Code movement is stopped by the guarded blocks

4. Select some block of normal code that is bellow some guarded section (type something bellow Variables declarations)
and press Shift+Alt+Up several times
-> Code is lost when it reaches guarded section

(Maybe a P4 because it is not a common use case? I find problematic mainly step 4...)
Comment 1 Jiri Prox 2008-09-04 14:58:48 UTC 
the step 4. is duplicate of issue 118875
Comment 2 Petr Dvorak 2008-09-04 15:00:37 UTC 
OK, therefore only step 2 is a problem (steps 1 and 3 are just to demonstrate difference between moving code up and
down). Thanks Jirka.
Comment 3 David Strupl 2009-03-31 15:53:26 UTC 
Resolving all issues with milestone "future" as LATER. If you feel strongly that
it should be implemented please reopen and set the target milestone to "next".
Comment 4 Quality Engineering 2009-11-02 10:58:06 UTC 
NetBeans.org Migration: changing resolution from LATER to WONTFIX