[Wesnoth-bugs] [bug #24511] Debug 'Create Unit' filter bug can cause unit not to be placed.

Update of bug #24511 (project wesnoth): Assigned to:None => gfgtdf ___ Reply to this item at: ___ Message

[Wesnoth-bugs] [bug #24511] Debug 'Create Unit' filter bug can cause unit not to be placed.

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

[Wesnoth-bugs] [bug #24186] Using a different keyboard layout causes letter based hotkeys not to work.

Follow-up Comment #8, bug #24186 (project wesnoth): BTW, thanks for your report on master - good to know it's not an issue with SDL2. ___ Reply to this item at:

[Wesnoth-bugs] [bug #24186] Using a different keyboard layout causes letter based hotkeys not to work.

Follow-up Comment #7, bug #24186 (project wesnoth): I think we understood your original complaint, I think Aginor was asking more about the state of the SDL2 build for your circumstances since that is the direction we are going. I have long since submitted PR #562 to revert all changes relating

[Wesnoth-bugs] [bug #24511] Debug 'Create Unit' filter bug can cause unit not to be placed.

Follow-up Comment #2, bug #24511 (project wesnoth): Thanks, that commit seems to have fixed it. I think the trouble you had with reproducing with my steps may be that you had add-ons with units in them, thus changing the line-up/reaction of the filter. I think I may have ran my instructions with

[Wesnoth-bugs] [bug #24511] Debug 'Create Unit' filter bug can cause unit not to be placed.

Follow-up Comment #1, bug #24511 (project wesnoth): I couldn't reproduce the bug with those steps exactly, but I did come across it in a slightly different manner. gfgtdf just made this commit to master: https://github.com/wesnoth/wesnoth/commit/1667e8680cdd9ee1e8c6b270fe6064caf70b2f27 And it

[Wesnoth-bugs] [bug #24511] Debug 'Create Unit' filter bug can cause unit not to be placed.

URL: Summary: Debug 'Create Unit' filter bug can cause unit not to be placed. Project: Battle for Wesnoth Submitted by: sigurdfdragon Submitted on: Wed 09 Mar 2016 05:57:22 PM UTC Category:

[Wesnoth-bugs] [bug #23318] Window Geometry not recognized

Follow-up Comment #19, bug #23318 (project wesnoth): The error message is a separate issue, already covered in bug #21564. ___ Reply to this item at: ___

[Wesnoth-bugs] [bug #24510] Scenario Name Label missing from Story Screens In Campaign Scenarios

URL: Summary: Scenario Name Label missing from Story Screens In Campaign Scenarios Project: Battle for Wesnoth Submitted by: sigurdfdragon Submitted on: Wed 09 Mar 2016 05:41:07 PM UTC

[Wesnoth-bugs] [bug #24186] Using a different keyboard layout causes letter based hotkeys not to work.

Follow-up Comment #6, bug #24186 (project wesnoth): I tested master & 1.13.4, hotkeys are fine there. :) This report is specifically for behavior on 1.12.5 as outlined in my OP. I should have been more specific at the time, but the way hotkeys are broken in 1.12.5 is that if have an different

[Wesnoth-bugs] [bug #23318] Window Geometry not recognized

also could not find a case where the drawing area was not the same as the clickable area. When a dialog is played out (e.g. campaign start) and I resize the window during that time, I can trigger the following error message: 20160309 15:45:51 error general: An error due to possibly invalid WML

[Wesnoth-bugs] [bug #23640] Read lua files from host.

Follow-up Comment #2, bug #23640 (project wesnoth): > Could this potentially be a security issue if we download arbitrary lua from the host and execute? THe host can also put arbitary [lua] tag in the scenario when its sends teh scenario to the clients, so i don't think this is somethign to

[Wesnoth-bugs] [bug #24226] Multiplayer player name displayed in singleplayer

Follow-up Comment #11, bug #24226 (project wesnoth): > Though the player name issue does seem resolved for both SP and MP. Hmm yes note that shoudl onyl happen with mp campaigns likw LoW and not with normal mp games. The reason for this beahviour is, that even when played in mp mode it happens

[Wesnoth-bugs] [bug #24509] Errors in gettext_boost.cpp when trying to build with Boost 1.60

Follow-up Comment #1, bug #24509 (project wesnoth): Hmm i also use boost 1.60 (on windows) and afaik this libary is build to work the same on all plattforms, so maybe something is wrong with your build configuration? ___ Reply to this item

[Wesnoth-bugs] [bug #23819] Non-ascii key not shown in hotkey preferences dialog.

Update of bug #23819 (project wesnoth): Assigned to:None => aginor Open/Closed:Open => Closed ___ Reply to this item at:

[Wesnoth-bugs] [bug #23673] Graphical errors around GUI elements in Wesnoth 1.13.1

Update of bug #23673 (project wesnoth): Open/Closed:Open => Closed ___ Reply to this item at: ___ Message

[Wesnoth-bugs] [bug #23488] All AI multiplayer crash

Update of bug #23488 (project wesnoth): Status:None => Upstream Problem Open/Closed:Open => Closed ___ Follow-up Comment #17: Thank you :) I'm

[Wesnoth-bugs] [bug #23488] All AI multiplayer crash

Follow-up Comment #16, bug #23488 (project wesnoth): Go ahead, it was a gcc/glibc issue triggered by wesnoth. ___ Reply to this item at: ___ Message sent via/by