https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362011-02-14T21:45:10ZEcoinformatics RedmineKepler - Bug #5286: Remove the override of EntityTreeModelhttps://projects.ecoinformatics.org/ecoinfo/issues/5286?journal_id=183082011-02-14T21:45:10ZDerik Barseghianbarseghian@nceas.ucsb.edu
<ul></ul><p>changing bugs from REAP to Kepler product</p> Kepler - Bug #5286: Remove the override of EntityTreeModelhttps://projects.ecoinformatics.org/ecoinfo/issues/5286?journal_id=183092012-03-28T21:32:12ZDerik Barseghianbarseghian@nceas.ucsb.edu
<ul></ul><p>I looked into removing this override a few ways, but things got convoluted. I think the best idea is to discuss incorporating the small change needed into ptolemy's EntityTreeModel.</p>
<p>If we want this override removed for the upcoming sensor-view release, this would mean releasing a patch of ptolemy-kepler-2.3.</p>
<p>In hopes of keeping the sensor-view release simple I'd just as soon keep the override in for now. If/when we patch ptolemy-kepler with the change, we could patch sensor-view at that point to remove the override.</p> Kepler - Bug #5286: Remove the override of EntityTreeModelhttps://projects.ecoinformatics.org/ecoinfo/issues/5286?journal_id=183102012-03-28T21:51:20ZMatt Jonesjones@nceas.ucsb.edu
<ul></ul><p>I would argue that we should incorporate it now and issue the patch. Overrides consistently diverge over time from their source, and we suffer from not picking up bug fixes, etc. In general, I think we should strive to eliminate all overrides ebfore release. They are a nice feature for experimental development, but make maintenance difficult if they are released. They also make it so that modules that use overrides become incompatible with other modules that don't use the override -- much better to have only one definitive source for a class (in this case, the ptolemy module) so that modules remain compatible.</p> Kepler - Bug #5286: Remove the override of EntityTreeModelhttps://projects.ecoinformatics.org/ecoinfo/issues/5286?journal_id=183112012-06-11T22:20:52ZDerik Barseghianbarseghian@nceas.ucsb.edu
<ul></ul><p>Sean can you confirm: am I right in thinking the point of the override was to avoid collapsing the Outline and Plotting's 'Items of Interest' trees when the actors fire? Possibly also to avoid collapses when the user moves the actor around, or adjusts the actor's params?</p>
Turns out, from what I can tell, this override actually isn't doing anything useful. With or without the override, this is what happens:
<ul>
<li>when firing, the trees don't collapse.</li>
<li>when moving or adjusting an actor's params, the trees collapse.</li>
</ul> Kepler - Bug #5286: Remove the override of EntityTreeModelhttps://projects.ecoinformatics.org/ecoinfo/issues/5286?journal_id=183122012-06-15T21:19:48ZDerik Barseghianbarseghian@nceas.ucsb.edu
<ul></ul><p>Removed at r29957. <br />Reopen this bug if you discover a change in component tree behavior in the sensor-view suite.</p> Kepler - Bug #5286: Remove the override of EntityTreeModelhttps://projects.ecoinformatics.org/ecoinfo/issues/5286?journal_id=183132013-03-27T21:29:53ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 5286</p>