Community
Participate
Working Groups
Found this while trying to reproduce bug 135121: In "Show Source of Selected Element Only", if you select a multi-line element, position at the last line, and start deleting lines with Ctrl-D, the editor will allow you to blindly delete lines from the next element without ever positioning on them.
This was like this since day one. No action for 3.2.
This feature (in conjunction with the quick outline) is awesome, however the fact that is so easy to delete code with no notice makes the current implementation too dangerous for me considering using it. Could this be considered for 3.3?
Sorry, we have other priorities for 3.3.
*** Bug 203164 has been marked as a duplicate of this bug. ***
I would like to request that the priority of this defect be bumped up to P1 Major - as this erroneous functionality is causing critical usability problems in our client code. For example, our editor, that is showing only the visible area of the code, is displaying the user code that is at the same time stored in some 'container object' in memory. When the user has finished using the editor, everything that is visible is stored back into the container object (later to be generated back to source code). At the same time the user code is available in a generated source file with specific tags above and below the code so that the user code is isolated. e.g. 1: void func() { 2: <some start tag> 3: userCode(); 4: 5: <some end tag> 6: } Now when the user preforms this multiple CTRL+D functionality at the end of the visible section (i.e. only lines 3 & 4 are visible), than they will delete lines 5 and 6. Undoing the CTRL+D actions, will result in lines 5 & 6 being visible (where as they should not be). This means when the user closes the editor the container object will be updated to contain the code with lines 5 and 6. Which in turn causes the users code to be invalid. In situations where the source code is generated, this will cause more problems as there will be two end tags, and extra '}'s. Please consider increasing the priority of the bug. Thanks in advance.
OK, let's fix this.
Fixed in HEAD. Available in 3.4 builds > N20070913-0010.
Created attachment 78322 [details] 3.3.2 Fix
Fixed in R3_3_maintenance.
.
Philippe, please approve. This is critical for a client (see comment 5).
+1 for 3.3.2
starting verification...
Verified in M20080123-0800.
