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.
The new code customizer in form editor allows to edit the code of property values inside the guarded blocks. E.g. add a JButton to a form and invoke Customize Code from context menu. Use combo box on the left to switch to "custom property" for the text property: jButton1.setText("jButton1"); Now part of the line - "jButton1" - is unguarded and selected. Try to type something - only the first char appears (that replaces the selected text). Now you can't edit on the last position before the guarded block (that should still be editable). It only works for the very first char placed between the guarded blocks.
Honzo, you probably know the most about guarded blocks at the moment. Could you please have a look at this? Is it java or editor problem? Thanks
I guess this has nothing to do with the editor/guards but with the GuardedDocument. You use NbDocumen.markGuarde/unmarkGuarded in order to permit custom editing, don't you?
Yes.
Then it is most likely a GuardedDocument's bug in the editor module.
*** Issue 109488 has been marked as a duplicate of this issue. ***
*** Issue 120127 has been marked as a duplicate of this issue. ***
moving opened issues from TM <= 6.1 to TM=Dev
*** Issue 136523 has been marked as a duplicate of this issue. ***
*** Issue 143606 has been marked as a duplicate of this issue. ***
Editor guys, is this difficult to fix? It significantly affects usability of the Customize Code dialog - people can't enter custom code for property values, the workaround is not obvious. The editor does not allow to insert character between guarded blocks at the last position. Would be nice if the target milestone 6.5 is right and the fix is planned :). Thanks
Just for the record, there is also a problem with guarded sections painting - see issue #135496.
As for the sections painting, isnt' it issue 133826? That's probably even more important - happens very often.
I'm just wondering, who is working on this issue? The workaround is rather bad and guard blocks are already annoying to work with. Please don't let this bug slip yet another release.
This seems to be already fixed in the latest dev build (probably after the fix of the famous "off-by-one bug" reported by gtzabari). Can you please have a look at it (and verify), tpavek?
This is the "off-by-one bug". The issue reported by gtzabari (153486) is the same thing, in addition it revealed that guarded blocks can be deleted via Ctrl+DEL. Thanks to that the off-by-one bug was fixed too.
Yes, I thought so;)... closing as fixed.