| Summary: | ContentOutline "Link with Editor" not working when switching between files | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Timo <timo.deuschle> |
| Component: | Xtext | Assignee: | Jan Koehnlein <jan> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chanskw, jan, mkomor, sven.efftinge, tmf.xtext-inbox |
| Version: | 2.0.1 | Flags: | sven.efftinge:
indigo+
|
| Target Milestone: | SR2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Timo
I also experienced the same problem with our editor. Looking at the code, looks like fLinkingEnabled has the wrong state. I wonder why we need to maintain a fLinkingEnabled state for each of the OutlineWithEditorLinker? Wouldn't it work if you just query the preference store for the latest preference setting before setting selection in the text/tree viewer? Just to confirm. This is targeted for SR2, does that mean this is targeted to the next 2.0 service release in Sept? Thanks... It will not be a service release but a full release (2.1) including new functionality and API. It is planned to be released in mid October. (In reply to comment #2) > I wonder why we need to maintain a fLinkingEnabled state for each of the > OutlineWithEditorLinker? Wouldn't it work if you just query the preference > store for the latest preference setting before setting selection in the > text/tree viewer? Selection events are quite frequent and AFAIK the preference store is much more than just a map, so caching this state might make sense Fix pushed to MASTER. Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |