Hi, people.
We're really near from 1.0 now. I'm working on releasing 1.0rc1, I had planned
to do it today, but I've used my time in writing a little script to help me
releasing the 1.0rcX and 1.0.x series. It's just a simple script that takes
the original tarball, strips TDH, the translations t
Since the developers have been discussing things to
fix before v1.0 I thought I should bring up these two
problems. I am using 0.9.7 for Mac OS X. Looking at
the
changelog I don't think these have been fixed in the
CVS version.
1. Prestart event commands appear on the screen.
It is true that in
Isaac Clerencia wrote:
1. Prestart event commands appear on the screen.
I've committed an attempt to fix this to CVS.
2. Halo graphics aren't being updated
I don't think we're going to be able to do anything to fix this before
1.0. Using haloes to try to make larger-than-hex units prob
This message has been caught by the list filter because it had a 3Mb
attachment.
I've uploaded the attachment to:
http://people.warp.es/~isaac/UTBS_test.zip
Here is the message content:
Bugs with prestart event and with changing halos
From: Asa Swain <[EMAIL PROTECTED]>
To: wesnoth-dev@gna.or
ott wrote:
I did not found proof of any memory leak when running the game under
valgrind's massif.
See the modified text in the version of the document in CVS, which notes
that the game uses lots of memory instead of discussing purported leaks.
I investigated why the game tends to take
On Sat, Sep 17, 2005 at 12:49:24PM +0200, Philippe Plantier wrote:
> >10962: a unit does not level up in a replay if that is the last action
> >
> >Sometimes one of your units will kill the last enemy leader and not only
> >win the scenario, but also receive enough experience points that it
> >leve
11966: the Map Editor does not allow the language to be changed
The Map Editor uses the language that the game was last played in. If
you want to use another language in the editor, change it in the game,
and then start the editor.
I partialy fixed this problem: pressing alt-l brings up the
On Fri, Sep 16, 2005 at 07:47:02PM -0500, David White wrote:
> I really think we should consider resolving this by choosing different
> shortcuts. Perhaps ctrl+c for command and ctrl+f for 'find' (if they're
> not already used).
Ctrl/Cmd-f would be nice for find, and would probably tie in with
e
