Complete.Org: Mailing Lists: Archives: freeciv-dev: October 2004:
[Freeciv-Dev] (PR#10475) mapview doesn't draw orders correctly
Home

[Freeciv-Dev] (PR#10475) mapview doesn't draw orders correctly

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: undisclosed-recipients: ;
Subject: [Freeciv-Dev] (PR#10475) mapview doesn't draw orders correctly
From: "Jason Short" <jdorje@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 7 Oct 2004 21:13:14 -0700
Reply-to: rt@xxxxxxxxxxx

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

Here's a patch.
? 1
? 2
? newtiles
Index: client/mapview_common.c
===================================================================
RCS file: /home/freeciv/CVS/freeciv/client/mapview_common.c,v
retrieving revision 1.152
diff -u -r1.152 mapview_common.c
--- client/mapview_common.c     7 Oct 2004 19:15:19 -0000       1.152
+++ client/mapview_common.c     8 Oct 2004 04:12:33 -0000
@@ -1676,7 +1676,7 @@
 bool show_unit_orders(struct unit *punit)
 {
   if (punit && unit_has_orders(punit)) {
-    struct tile *ptile = punit->tile, *tile1;
+    struct tile *ptile = punit->tile;
     int i;
 
     for (i = 0; i < punit->orders.length; i++) {
@@ -1693,8 +1693,8 @@
       switch (order->order) {
       case ORDER_MOVE:
        draw_segment(ptile, order->dir);
-       tile1 = mapstep(ptile, order->dir);
-       if (!tile1) {
+       ptile = mapstep(ptile, order->dir);
+       if (!ptile) {
          /* This shouldn't happen unless the server gives us invalid
           * data.  To avoid disaster we need to break out of the
           * switch and the enclosing for loop. */

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