[Wesnoth-bugs] [patch #1165] improved version of 'xp sort'

Follow-up Comment #5, patch #1165 (project wesnoth): I already committed a combined sorter weeks ago for bug #13360; this patch just improves upon it. If you think this is a bad idea, then what alternative semantics do you propose? ___ Re

[Wesnoth-bugs] [bug #13437] AMLA XP text in sidebar hard to read

Follow-up Comment #1, bug #13437 (project wesnoth): Looking through the code, if I recall correctly, it appears Wesnoth is using 100-0-160. If we were to use instead, say, 160-0-255, which is almost exactly the same hue but about 20% brighter, I think this would stand out better. (file #5725)

[Wesnoth-bugs] [bug #13448] Description of Add-ons when browsing items on server

URL: Summary: Description of Add-ons when browsing items on server Project: Battle for Wesnoth Submitted by: ancestral Submitted on: Wednesday 04/29/2009 at 04:49 Category: Feature Request

[Wesnoth-bugs] [bug #13447] Sometimes Halt at 0% when connecting to an Official Server

URL: Summary: Sometimes Halt at 0% when connecting to an Official Server Project: Battle for Wesnoth Submitted by: mamus Submitted on: Wednesday 04/29/09 at 04:19 Category: Bug

[Wesnoth-bugs] [bug #13432] Dependency Text

Follow-up Comment #3, bug #13432 (project wesnoth): Yes, I think having the name of the add-on would be better. Don't you agree? :) Hopefully you haven't taken my emphasis out of context, it was not meant as being condescending or disrespectful. Just kinda had a realization and I wanted to label

[Wesnoth-bugs] [bug #13420] Dialogue window resize error

Follow-up Comment #2, bug #13420 (project wesnoth): Just tested with the 1.6 branch and the bug is not there. (Part of the fix will still apply to 1.6 but the way it's triggered seems a new bug in trunk.) ___ Reply to this item at:

[Wesnoth-bugs] [bug #13333] Text Input Crashes Wesnoth

Follow-up Comment #6, bug #1 (project wesnoth): Ignore my last comment, posted in the wrong report. ___ Reply to this item at: ___ Message sent via/by Gna!

[Wesnoth-bugs] [bug #13333] Text Input Crashes Wesnoth

Follow-up Comment #5, bug #1 (project wesnoth): Just tested with the 1.6 branch and the bug is not there. ___ Reply to this item at: ___ Message sent via/by

[Wesnoth-bugs] [patch #1028] Clarify error message when castles are unplacable on generated map

Update of patch #1028 (project wesnoth): Status: Postponed => Wont Do ___ Follow-up Comment #13: No more work on this one over more than half a year, no reaction from the original poster. As

[Wesnoth-bugs] [patch #1165] improved version of 'xp sort'

Follow-up Comment #4, patch #1165 (project wesnoth): As I said on IRC to corn and what boucman also said, I think the combining of two sorters is also bad design. I also don't intent to include that feature in the new gui, so please don't commit that feature.

[Wesnoth-bugs] [patch #1165] improved version of 'xp sort'

Update of patch #1165 (project wesnoth): Assigned to:mordante => dfranke ___ Follow-up Comment #3: I'm sick ATM, but I will review and probably commit this patch sometime soon. ___

[Wesnoth-bugs] [bug #13397] nearest_keep returns occupied keeps when there are empty keeps in the same distance

Update of bug #13397 (project wesnoth): Status:None => Fixed ___ Reply to this item at: ___ Message sen

[Wesnoth-bugs] [bug #13445] FAI has problems with unary - (minus)

URL: Summary: FAI has problems with unary - (minus) Project: Battle for Wesnoth Submitted by: benetnash Submitted on: Tuesday 04/28/2009 at 17:17 Category: Bug Severity: 2 - Mi

[Wesnoth-bugs] [bug #13440] Using the [kill] tag causes Wesnoth to crash

Update of bug #13440 (project wesnoth): Item Group:None => None of the others ___ Follow-up Comment #2: Can be related to https://gna.org/bugs/?13256

[Wesnoth-bugs] [bug #13440] Using the [kill] tag causes Wesnoth to crash

Follow-up Comment #1, bug #13440 (project wesnoth): I should have said: this bug occurs on mainline maps and default era, but only if you have my Galactic Empires add-on installed. I also think you might need to have fog on to make it crash. _

[Wesnoth-bugs] [bug #13170] [switch]/[case] should work within [part]

Update of bug #13170 (project wesnoth): Status: Ready For Test => Fixed ___ Follow-up Comment #5: >From the #wesnoth-dev IRC channel: 14:23 Testing... 14:26 Shadow_Master: Looks good. Feel f

[Wesnoth-bugs] [bug #13290] [if] and [switch] should work within [part]

Update of bug #13290 (project wesnoth): Item Group:None => None of the others Status:None => Fixed ___ Follow-up Comment #2: >From the #wesnoth

[Wesnoth-bugs] [bug #13432] Dependency Text

Follow-up Comment #2, bug #13432 (project wesnoth): One response: There's nothing wrong with using the name of the add-on itself. I was just submitting the solution as *you* proposed it, so if *you* want to change it, go ahead. I am sure that such a solution would be possible. ___

[Wesnoth-bugs] [bug #13441] stable-changelog.wesnoth.org still points to 1.4 branch

Update of bug #13441 (project wesnoth): Status:None => Fixed Open/Closed:Open => Closed ___ Follow-up Comment #1: Thanks for the rep

[Wesnoth-bugs] [patch #1170] Partial fix for nondeterministic Formula AI methods

Follow-up Comment #3, patch #1170 (project wesnoth): You're right, I added two additional comparsions - for attacker and defender weapon (defender weapon comparsion is redundant) (file #5720) ___ Additional Item Attachment: File name: do_

[Wesnoth-bugs] [patch #1141] Graphics optimization

Follow-up Comment #10, patch #1141 (project wesnoth): (Note that you patch contains a lot of trailing tabulations. You already did a mess with your pathfinding commit; so please fix your editor settings, change your editor, or use a script to remove them automatically.) The algorithm looks a lot