[Commits] [wesnoth/wesnoth] 53e792: Avoid crash when planning moves on planned recruit...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/wesnoth/wesnoth
  Commit: 53e79232e7a9bef7e67720cb9e108617ece55b8b
      https://github.com/wesnoth/wesnoth/commit/53e79232e7a9bef7e67720cb9e108617ece55b8b
  Author: Wedge009 <wedge009 at wedge009.net>
  Date:   2015-11-05 (Thu, 05 Nov 2015)

  Changed paths:
    M changelog
    M src/whiteboard/move.cpp

  Log Message:
  -----------
  Avoid crash when planning moves on planned recruits (Bug #18637)

Attempt to work-around bug #18637, where planning moves on planned recruits results in a crash (because get_unit() is null when move::init() is called).

This isn't a comprehensive fix because clicking on a planned recruit will still result in the usual display feedback for planning a move. The difference here is that attempting to place a planned move will result in nothing happening when the mouse button is clicked (as opposed to the assertion failure or crash which happens currently). It is better than nothing, I believe, unless there are negative side-effects of which I am unaware of.

As per the bug report, the ideal solution is to either get planned moves on planned recruits working properly, or disallow this movement altogether.


  Commit: e5538b3ad8b740d967570bf544ee7ca7dfe21ced
      https://github.com/wesnoth/wesnoth/commit/e5538b3ad8b740d967570bf544ee7ca7dfe21ced
  Author: Ignacio R. Morelle <shadowm at wesnoth.org>
  Date:   2015-11-05 (Thu, 05 Nov 2015)

  Changed paths:
    M changelog
    M src/whiteboard/move.cpp

  Log Message:
  -----------
  Merge pull request #497 from Wedge009/bug_18637_fix

Work-around for planning moves on planned recruits (bug #18637)


Compare: https://github.com/wesnoth/wesnoth/compare/b874d4d302b9...e5538b3ad8b7