Looks good!
On 18/06/2010, at 5:52 AM, Andrea Aime wrote:
> Andrea Aime ha scritto:
>> Jody Garnett ha scritto:
>>> On 17/06/2010, at 10:36 PM, Andrea Aime wrote:
>>>
Let's say the renderer would become... more aware of dpi.
It's actually already considering the dpi hint when it comes
Andrea Aime ha scritto:
Jody Garnett ha scritto:
On 17/06/2010, at 10:36 PM, Andrea Aime wrote:
Let's say the renderer would become... more aware of dpi.
It's actually already considering the dpi hint when it comes to compute
the scale.
The rescale visitor would not go, that's actually the bi
Jody Garnett ha scritto:
On 17/06/2010, at 10:36 PM, Andrea Aime wrote:
Let's say the renderer would become... more aware of dpi.
It's actually already considering the dpi hint when it comes to compute
the scale.
The rescale visitor would not go, that's actually the bit of code I
want to use t
On 17/06/2010, at 10:36 PM, Andrea Aime wrote:
> Let's say the renderer would become... more aware of dpi.
> It's actually already considering the dpi hint when it comes to compute
> the scale.
>
> The rescale visitor would not go, that's actually the bit of code I
> want to use to perform dpi r
Jody Garnett ha scritto:
> Thanks for bringing that context back to the discussion (I somehow
> missed it arriving partway along in the discussion).
>
> I am interested in seeing this happen as: - it is not wms specific -
> we run into this issue when printing from uDig - it really is not wms
> sp
Thanks for bringing that context back to the discussion (I somehow missed it
arriving partway along in the discussion).
I am interested in seeing this happen as:
- it is not wms specific - we run into this issue when printing from uDig
- it really is not wms specific; we are starting to run into
