Re: [Viking-devel] maps download problem

[Reid P. <re...@re...>]

Guilhem Bonnefille wrote:
> On 8/23/07, Quy Tonthat <qto...@gm...> wrote:
>> Guilhem Bonnefille wrote:
>>> 2) Each time a map layer is created, automatically change the view
>>> mode to the mode supported by the layer.
>> This will cause more confusion to users by hiding the fact that
>> they have to deal with viemode menu for now.
> 
> Other idea, only for the map layer's creation: when a map layer is
> created, Viking should inform the user that current view mode is
> incorrect, and propose to solve this for the user.
> This sort of action is current nowaday. For example, Eclipse propose
> to the user to switch to the "Team Synchronisation view" when the user
> requests an action that need this view.
> 
> Other idea: Viking should hide (inactive) the map layer that cannot be
> rendered in the current view. By this way, the user can understand
> that something is wrong. This is the main problem IMO: the user
> currently has no mean to "naturaly" discover that its current
> configuration is wrong.

I agree with Quy: for now, I'd suggest implementing the minimum band-aid 
necessary to inform the user that there are different view modes. 
Perhaps: after the user adds a new layer or Viking starts up, you check 
if all the map layers use the same draw mode. If not, just display a 
dialog box explaining that there are different view modes, and some map 
layers won't display for this reason.

For long-term, I wonder if the way to do it is to use GDAL to warp tiles 
to some common draw mode (projection) when they are downloaded. (There 
would need to be a way to convert existing tile sets.) One drawback that 
may turn out to be significant is that the tiles may look bad when warped.

Reid