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: | [2004-04-22] Elements and selection | ||
---|---|---|---|
Product: | platform | Reporter: | Jaroslav Tulach <jtulach> |
Component: | Window System | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | mkleint, tpavek |
Priority: | P2 | ||
Version: | 4.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | TASK | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 41085 |
Description
Jaroslav Tulach
2004-03-24 17:20:25 UTC
So you need reference to the swing component of other elements, right? The only problem from the multiview API side I can see, is that the creation of the elements from descriptions should be done inside the multiview module. So I will need to add a query that allows the client code to obtain the correctly created MultiViewElement instance from the framework. Not necessarily. Form editor now opens the java source editor by calling JavaEditor.openAt(...) - which calls EditorSupport.openAt(...) which calls requestActive on the Editor copmponent etc. So I need this to keep working the same way somehow - i.e. open/select the JavaEditor (and jump to the right position). If this could not work (transparently), then form editor would need a way to open/select the java editor first before calling openAt on it. reassigning changes made to EditorSupport and related files to support this scenario. a sketch implementation in form module (branch multiview_march2004) behaves as described in the report. |