| Summary: | logic diagram example: LED doesn't reset to zero when wires disconected | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | Brendan Curran-Johnson <brendanc> | ||||
| Component: | GEF-Legacy GEF (MVC) | Assignee: | Alexander Nyßen <nyssen> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | trivial | ||||||
| Priority: | P3 | CC: | ahunter.eclipse, nyssen | ||||
| Version: | 3.4 | ||||||
| Target Milestone: | 3.10.0 (Mars) M2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Brendan Curran-Johnson
Created attachment 131911 [details]
Delete the connection, but the LED value is not changed.
This bug also occurs in Build: I20090411-1031
Platform: Windows Vista, Windows XP
Affected Locale(s): Korean, SChinese, TChinese, Turkish(pls see TR_1.gif)
Fixed implementation of LED#update(), which did not reset the bit values in case there is no connection present. Changed committed to cvs HEAD as well as R3_7_maintenance branch. Also updated org.eclipse.gef.examples.ui.pde zip files in both branches. It seems the implemented fix broke the increment/decrement functionality. As the LED is somehow a mixture of Hex-Switch and Hex-Display, I think a consistent behavior could be as follows: - if no input is present, show the local value, and allow it to be increase/decreased. - if input is present, use that input, ignore any increase/decrease. This way, upon disconnect, it will use the value that has been set (via increase/decrease) before being connected. Implemented the more consistent behavior outlined before. Changes pushed to origin/master. Resolving as fixed in 3.10.0M2. |