Are cylindrical worlds not fully supported?

[dancebob at mindspring dot com (Bob Carragher)]

Hello,

Please forgive an old ML lurker returning to the list
only to ask a question that has probably been answered.
Unfortunately, I have been unable to find that answer
in the ML archives.  Any help would be greatly appreciated!

My question is, basically, Are cylindrical worlds fully
supported or not?

I have seen unusual behavior when panning and when units
reach the border.  There are three examples that I can
reproduce.

     1.  In the standard game, use the GUI to set the
         world circumference equal to the width.  Then
         start the game.

         The world map is strangely displayed as a
         slightly skewed triangle of black (with a
         malformed top corner) in a grey background,
         with the part of the world visible to the
         player located in the proper location.

         I have created a variant of the standard game
         in which the world circumference is equal to
         its width.  i.e.

              (world-size (60 30 60))

         This will allow one to start the game directly,
         without needing to set the circumference through
         the GUI, and see the behavior immediately.

     2.  If you quit the above game, or start it with option
         "World Seen," then panning stops at the horizontal
         edge of the world as seen in the world map portion.
         However, if this is a cylindrical world, shouldn't
         the panning continue indefinitely?  Also, the
         redrawing is imperfect, as the edge hexes and roads
         are repainted half-corrupted.

     3.  If you create, for example, a troop transport and
         move it to the horizontal edge of the world as seen
         in the world map portion, you will sometimes "lose"
         it.  That is, you can still make it perform some
         actions, such as movement, but it cannot be found
         in the map view until you move it away from the edge.

I can provide screen shots for each of these to illustrate
the textual description, but I figured I'd start with a
relatively small posting.  ^_^;;;;

Also, if it's a problem with my setup, I can provide details
on the installation base, versions, and so forth.  To start
things off, I'm seeing this behavior on xconq version 7.4.1
which was built using gcc 3.0 (although I also saw this
behavior with version 7.3.2 built using gcc 2.95.2).  This
was linked with Tcl/Tk version 8.0.4.  It is run on Linux
(kernel version 2.2.14).

Any help or pointers to fixing these problems would be greatly
appreciated.

My apologies for such a long message!

Thanks!

				Bob