Your message dated Thu, 6 Nov 2008 08:32:12 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#473909: wesnoth: CTK/CTBK calculator needs
optimization and responsiveness
has caused the Debian Bug report #473909,
regarding wesnoth: CTK/CTBK calculator needs optimization and responsiveness
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
473909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473909
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: wesnoth
Version: 1:1.4-1
Severity: normal
When one unit attacks another, Wesnoth calculates the chance to kill
(CTK) and chance to be killed (CTBK) for each possible attack, and
then suggests the attack it deems optimal. Clicking the "details"
button gives the actual CTK/CTBK percentages and the damage
histograms.
Many popular Wesnoth scenarios, such as SurvivalXtreme, offer the
ability to upgrade a unit by spending gold at a shop. In these
scenarios, battles may regularly occur between units that have
thousands of HP, high resistance, high defense, and berserk weapons.
This causes the CTK/CTBK calculation to take an excessively long time,
sometimes up to several minutes in extreme cases; during this time,
Wesnoth does not respond to user input and does not redraw its window.
Furthermore, when clicking the "details" button, Wesnoth again takes
an exceedingly long time, suggesting that it recalculates the data
rather than saving it.
Ideally, Wesnoth's CTK/CTBK calculator should not take this long to
return results. In any case, it should not completely block the user
interface while running, should not recalculate the same data when
providing further details, and should give some kind of progress
indicator while running.
- Josh Triplett
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages wesnoth depends on:
ii libboost-iostreams1.34 1.34.1-10 Boost.Iostreams Library
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libfreetype6 2.3.5-1+b1 FreeType 2 font engine, shared lib
ii libfribidi0 0.10.9-1 Free Implementation of the Unicode
ii libgcc1 1:4.3.0-2 GCC support library
ii libsdl-image1.2 1.2.6-3 image loading library for Simple D
ii libsdl-mixer1.2 1.2.8-3 mixer library for Simple DirectMed
ii libsdl-net1.2 1.2.7-2 network library for Simple DirectM
ii libsdl1.2debian 1.2.13-2 Simple DirectMedia Layer
ii libstdc++6 4.3.0-2 The GNU Standard C++ Library v3
ii libx11-6 2:1.1.3-1 X11 client-side library
ii python2.4 2.4.5-1 An interactive high-level object-o
ii wesnoth-data 1:1.4-1 data files for Wesnoth
ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime
wesnoth recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
* Mark de Wever <[EMAIL PROTECTED]> [2008-04-02 20:25:53 CEST]:
> Since the current way works properly for mainline content and the
> problem has been brought to the attention of addon developers we won't
> fix this problem in the foreseeable future.
As Mark's mail hasn't received any response since april I am now
closing this wontfix bug. There is no way this will get fixed inside
Debian, so if you still think this issue is valid please bring it up in
the upstream tracker: <https://gna.org/bugs/?group=wesnoth>
Thanks,
Rhonda
--- End Message ---
