|
From: Quy T. <qto...@gm...> - 2007-08-23 17:14:00
|
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. That's what I intend to do. Pointing users to the view menu and suggest what mode they should choose for downloading. This won't solve "viewmode problems" in overall though. > > 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. Hiding layers, IMHO, takes a lot of work. I'd rather spending the time in solving the problem properly, which is getting rid of viewmode completely. Quy |