On Sat, 27 Aug 2011, Stefan Breunig wrote:
More important though: to achieve this I create the map frame once on
start and never destroy it. Is there any disadvantage I missed? I know
about the bug where the view in the download diag is reset to 0.0, 0.0
and that code depending on notifyMapFrame
On 08/27/2011 11:02 AM, Dirk Stöcker wrote:
> On Sat, 27 Aug 2011, Stefan Breunig wrote:
>
>> More important though: to achieve this I create the map frame once on
>> start and never destroy it. Is there any disadvantage I missed? I know
>> about the bug where the view in the download diag is rese
> Basically all plugins implement mapFrameInitialized. Does this
> method with two arguments still make sense, when your patch is
> applied?
No, my plan was to get rid of it altogether so plugins can simply use
Main.map or similar to get the MapFrame. Since it would never be
destroyed there would
On 08/27/2011 01:03 PM, Stefan Breunig wrote:
>> Basically all plugins implement mapFrameInitialized. Does this
>> method with two arguments still make sense, when your patch is
>> applied?
>
> No, my plan was to get rid of it altogether so plugins can simply use
> Main.map or similar to get the M
