| Summary: | [Model browser] stays on "loading..." indefinitely | ||
|---|---|---|---|
| Product: | [Modeling] MoDisco | Reporter: | Nicolas Bros <nicolas.bros> |
| Component: | Infrastructure | Assignee: | Nicolas Bros <nicolas.bros> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | hugo.bruneliere, modisco.web-inbox |
| Version: | 0.9.0 | Flags: | nicolas.bros:
indigo+
|
| Target Milestone: | 0.9.0 M7 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Nicolas Bros
Fixed in revision 4214. I have added an explicit refresh after the value (children, text, image, ...) is computed, instead of relying on an indirect refresh through a model change notification that was supposed to trigger the refresh through a chain of events. I extracted the asynchronous computing functionality into a new class NonBlockingElementComputation<T>, and I generalized it for each possibly blocking computation done by either the label or content providers. The way it works is that it computes a value synchronously initially, and then it continues asynchronously if the computation takes too much time (> 200ms per computation). I also fixed the "browse" functionality, so that it waits for the element to be displayed (after a refresh) until it attempts to select it. Bug solved. |