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

[Charles Dang]

Update of bug #24511 (project wesnoth):

 Assigned to:None => gfgtdf 


___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Charles Dang]

Update of bug #24511 (project wesnoth):

  Status:None => Fixed  


___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Wedge009]

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:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Wedge009]

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 to hot-keys in 1.12 branch (which will resolve your issue at
the expense of bringing back other hot-key bugs) but no-one has given it much
attention since then. At the very least, it doesn't look like 1.12.6 is
intended for release any time soon.

___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[SigurdFireDragon]

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 the --noaddon flag and forgot to
mention that.

___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Charles Dang]

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 seems to fix the behavior for me. Could you test again?

___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[SigurdFireDragon]

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: Bug
Severity: 3 - Normal
Priority: 5 - Normal
  Item Group: User Interface
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
 Release: 1.13.4+dev
Operating System: Win 7 x64

___

Details:

This has been around for at least 2 months.
Posting now because I finally figured out the circumstances it was occurring
under.

A bug can occur in debug 'Create Unit', such that placing a unit will not work
when it is attempted. This involves using the filter.

To reproduce, follow these steps:

1. Open Create Unit dialog.
2. Type 'Sl' into the filter.
3. Delete the 'l' that was just typed.
4. Type a 'y'  (the filter should now contain 'Sy').
5. Either double click on 'Elvish Sylph' or click it and click ok.
6. The unit is not spawned.





___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Wedge009]

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:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[SigurdFireDragon]

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
Category: Bug
Severity: 3 - Normal
Priority: 5 - Normal
  Item Group: Campaign
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
 Release: 1.13.4
Operating System: Win 7 x64

___

Details:

The label that has the Scenario name on the story screen when the journey
tracks are being posted is now missing.
In 1.12.5, the label appears when the journey tracks are being animated.

Just start any campaign with journey tracks to test (such as AOI)




___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[SigurdFireDragon]

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 layout in windows and start the game,
you can set hotkeys, but if you quit wesnoth, then restart, the saved values
become useless, and the keys need to be reassigned again. (there might be
something else as well)

This means anyone with an alt layout would have to switch to qwerty before
launching wesnoth to avoid the issue.

It's not an issue for me personally, because I compiled my own version of
1.12.5 with the commit in question reverted.

___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Johannes Jordan]

Follow-up Comment #18, bug #23318 (project wesnoth):

With 1.13.4 the issue is much better and different.
In many cases, the window gets redrawn correctly.
In some cases, Wesnoth still operates in the old, smaller resolution, until I
click somewhere (but clicking helps! and it did not before).
I 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
occurred
The error message is :
Failed to show a dialog, which doesn't fit on the screen.

When reporting the bug please include the following error message :
src/gui/widgets/window.cpp:1074 in function 'layout' found the following
problem: Failed to size window; wanted size 3322,98 available size 1091,667
screen size 1273,697.



However I think it rarely occurs that someone resizes the window during a
dialog.

To conclude, it is not perfect but much better with 1.13.4.

___

Reply to this item at:

  <http://gna.org/bugs/?23318>

___
  Nachricht gesendet von/durch Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Daniel]

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 worry about.

___

Reply to this item at:

  

___
  Nachricht gesendet von/durch Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Daniel]

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 quite often in those campaigns that one player constorls
multiple sides so displaying the players name might not be enough. Note that
in some dialogs where it makes sense  the current_player string is also used
in this case.

> If the above is unrelated to this bug I will create a new one
Yes please do that.

> But I am wondering if tinkering with the game engine code has done anything
to break handling of teams/players/leaders.

Yes there area lot of changein that code between 1.12 and master although most
likeley not related to this bug.

___

Reply to this item at:

  

___
  Nachricht gesendet von/durch Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Daniel]

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 at:

  

___
  Nachricht gesendet von/durch Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Ignacio R. Morelle]

Update of bug #23819 (project wesnoth):

 Assigned to:None => aginor 
 Open/Closed:Open => Closed 


___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Ignacio R. Morelle]

Update of bug #23673 (project wesnoth):

 Open/Closed:Open => Closed 


___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Andreas Löf]

Update of bug #23488 (project wesnoth):

  Status:None => Upstream Problem   
 Open/Closed:Open => Closed 

___

Follow-up Comment #17:

Thank you :)

I'm marking as upstream and closing.

___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

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

[Pee Vee]

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 Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs