Opened 17 years ago
Closed 15 years ago
#117 closed defect (fixed)
Different handling in function "Export to logical model"
| Reported by: | mirschel | Owned by: | mirschel |
|---|---|---|---|
| Priority: | major | Milestone: | Promot 0.8.3 |
| Component: | PromotGuiVizNav | Version: | 0.8.0 |
| Severity: | bad | Keywords: | export logical model |
| Cc: |
Description (last modified by rempel)
The option "Export to logical model" have two different flavors. One is used by the editor where the mdl coordinates but no graphics are exported (call from the central import-export menu in browser). The other option is using the explorer. Here, the coordinates of the explorer-graphics and the graphics are exported (call from the explorer menu). The ordinary user is the explorer way because the user gets nicer networks.
For new users it is hard to find the explorer option because the browser option is more central but in practice less important. Also the differences are not obvious and therefore it could be confusing. Both option should be unified in some way.
Change History (10)
comment:1 Changed 17 years ago by mirschel
- Keywords export logical model added
- Milestone set to first_release
- Version set to 0.8.0
comment:2 Changed 17 years ago by rempel
- Resolution set to fixed
- Status changed from new to closed
comment:3 Changed 17 years ago by rempel
- Milestone changed from Promot 1.0 to Promot 0.8.2
comment:4 Changed 17 years ago by rempel
- Component changed from PromotGuiBase to PromotGuiVizNav
- Resolution fixed deleted
- Status changed from closed to reopened
although the changes from r7894 were working it resulted in always starting an explorer which for large models is quite time consuming, so it was refactored to start the explorer only when explicitly demanded in dialog when started from browser (option to export vai explorer from browser). Both initial working ways to export logical models (browser without explorer and from explorer) are working. The first export from the browser using the explorer results in an java.awt.geom.IllegalPathStateException?: missing initial moveto in path definition ... at org.mpg.dcts.promot.viznav.NavEdgeView?.paint(NavEdgeView?.java:1329) (changes, error probably only showing here, NavNode? paint also possible) ... at org.mpg.dcts.promot.dialogs.CmdStructureExport?.saveImage(CmdStructureExport?.java:174)
The reason seems to be that the explorer has not completed initialization although the scenarios are reported to be applied. Looks like a concurrency issue (maybe stale data?).
As exports using the explorer work after this exception the workaround right now is that after this exception the model can be exported again, which than works without problems.
comment:5 Changed 17 years ago by rempel
- Description modified (diff)
null pointer for explorer after export (only important for trying to export one model multiple times from the same dialog, but needs at least some error handling). the initial path error is now a ticket in its own #158.
comment:6 Changed 16 years ago by rempel
- Milestone changed from Promot 0.8.2 to Promot 0.9
comment:7 Changed 16 years ago by mirschel
- Status changed from reopened to new
The error with 'missing initial moveto in path definition exception' is now discussed in detail in ticket #176.
comment:8 Changed 16 years ago by mirschel
- Status changed from new to assigned
comment:9 Changed 15 years ago by mirschel
- Milestone changed from Promot 0.9 to Promot 0.8.3
comment:10 Changed 15 years ago by mirschel
- Resolution set to fixed
- Status changed from assigned to closed
Solved by r9198. Model can now be exported multiple times from the same dialog with or without Explorer.
fixed with rev. 7894 (explorer is started if necessary, so both commands are using the explorer now)