Ticket #648 (closed defect: fixed)
Opened 2011-06-28T17:21:46-05:00
Last modified 2011-07-11T15:56:58-05:00
Eliminate static class variables from legacy layer
| Reported by: | bdezonia | Owned by: | bdezonia |
|---|---|---|---|
| Priority: | major | Milestone: |
|
| Component: | Legacy Compatibility | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: |
Description
LegacyManager has the static variables and methods associated with tracking whether we're inside a IJ1 plugin at the moment. Eliminate this static code. Perhaps just remove static access and have interested users query for the current LegacyManager and access the API as needed.
Change History
comment:1 Changed 2011-07-08T13:49:52-05:00 by bdezonia
comment:2 Changed 2011-07-11T15:56:58-05:00 by bdezonia
- Status changed from new to closed
- Resolution set to fixed
We decided this was not needed. Found alternate implementation to fix IJ1 closing IJ2 window bug in 51d01814a1ea2407baaf6a19b2bc7491ea5bea4b.
It looks like someone removed this already. But the functionality of insideIJ1Plugin() is now unimplemented. Will discuss with Curtis whther we need this functionality.