On Fri, May 6, 2011 at 3:13 AM, Michael Bedward
wrote:
> Hi Jody,
>
>> you are brave!
>>
>
> No, just foolish. See aaime's unhappy comment on the Jira:
> http://jira.codehaus.org/browse/GEOT-3565
>
> He assumes it will break everything, although the setter and getter
> for MapContext are still the
>
> It's hard to see what the point of having MapContent, Layer etc is if
> they can't be used with other classes in the same module. And if the
> renderer can't change, the swing module is stuck with MapContext too.
>
Yeah this is my own personal tear; the MapLayer class was getting to be so
magi
Hi Jody,
> you are brave!
>
No, just foolish. See aaime's unhappy comment on the Jira:
http://jira.codehaus.org/browse/GEOT-3565
He assumes it will break everything, although the setter and getter
for MapContext are still there, just deprecated and the patch is meant
only for trunk.
It's hard t
you are brave!
--
Jody Garnett
On Thursday, 5 May 2011 at 8:46 PM, Michael Bedward wrote:
> On 5 May 2011 20:28, Jody Garnett wrote:
> > Actually would do better to create a Jira with a patch.
>
> I'm onto it
>
> Michael
>
On 5 May 2011 20:28, Jody Garnett wrote:
> Actually would do better to create a Jira with a patch.
I'm onto it
Michael
--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and c
No good suggestion; looks like we should round up a list of gottchas and talk
to aaime about changing GTRender interface.
public void setContext( MapContext context );
public MapContext getContext();
Actually would do better to create a Jira with a patch.
--
Jody Garnett
On Thursday, 5 May 201
