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: | glyphs should be serialized. | ||
|---|---|---|---|
| Product: | platform | Reporter: | Jan Jancura <jjancura> |
| Component: | Text | Assignee: | David Konecny <dkonecny> |
| Status: | VERIFIED WONTFIX | ||
| Severity: | blocker | CC: | jtulach |
| Priority: | P2 | Keywords: | ARCH |
| Version: | 3.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | |||
| Bug Blocks: | 21748 | ||
|
Description
Jan Jancura
2002-04-15 14:48:37 UTC
Set target milestone to TBD Set target milestone to TBD Adding ARCH keyword. I'd like to know what component is supposed to serialize those things. Whether it is right that debugger keeps it, or if really editor support should serialize them? The second seems to me it is not the desired behaviour. It is definitively bad that debugger module has to do some work during startup. Doing that only because one needs to initialize breakpoints (especially for not opened editor windows) is bad. In my opinion the editor infrastructure should remember all (persistent) glyphs and initialize them only when needed. reassigne to David K., new owner of editor I might be missing something but from the short description of the problem I tend to disagree with this enhancement. The debugger has to persist breakpoints with their specific data anyway and so it seems to me natural that debugger should add/remove annotations to a document and be responsible for their persistence. If there is no way to learn when the document is opened in editor and when the breakpoints should be deserialized and shown then file separate issue. Agreed with David's solution - verifying. |