Complete.Org: Mailing Lists: Archives: freeciv-dev: November 2004:
[Freeciv-Dev] Re: (PR#8998) Small map meets large screen, they have prob
Home

[Freeciv-Dev] Re: (PR#8998) Small map meets large screen, they have prob

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: vasc@xxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#8998) Small map meets large screen, they have problems together.
From: "Gregory Berkolaiko" <Gregory.Berkolaiko@xxxxxxxxxxxxx>
Date: Mon, 29 Nov 2004 22:23:42 -0800
Reply-to: rt@xxxxxxxxxxx

<URL: http://rt.freeciv.org/Ticket/Display.html?id=8998 >

> Solution 1.  Disable the copy-on-scroll cached drawing mechanism when
> the mapview gets too large.  This can either be done automatically or as
> a client option.  Advantage: easy and sure.  Disadvantages: very slow -
> this is a particular problem since the mapview is guaranteed to be large
> with this happens.
>
> Solution 2.  Draw all tiles on the mapview, including duplicated tiles.
>  This means the cached system will continue to work.  Advantages:
> retains speed, and allows duplicated tiles.  Disadvantages: harder to
> implement, bug-prone, allows duplicated tiles.
>
> Solution 3.  Restrict the maximum size of the mapview in mapview_common.
>  If the mapview gets too big some parts of it just aren't shown.
> Advantages: retains speed, easy to implement.  Disadvantages: the whole
> mapview can never be shown.

I would go for (3), the lazy option





[Prev in Thread] Current Thread [Next in Thread]