mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/773

This issue needs to be closed and there is no appropriate status, so
will set it to "Opinion" just for migration purposes.

** Bug watch added: github.com/Mudlet/Mudlet/issues #773
   https://github.com/Mudlet/Mudlet/issues/773

** Changed in: mudlet
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1383998

Title:
  Code to keep track of area coordinate extremes incomplete

Status in Mudlet:
  Opinion

Bug description:
  Whilst fixing TArea::exits I spotted that the code that maintained the
  coordinate extremes in the x, y and z dimensions:
  "TArea::{min|max}_{x|y|z}" for the TArea classes and the x and y
  extremes for each used z axis value (there are also redundant values
  for the z axis): {x|y|z}{min|max}Ebene has been commented out and
  seems incomplete.  I suspect that work needs to be done in this area.

  One positive outcome for that is that it should be possible to improve
  both the 2 and 3D mapper widgets if they can be revised to use this
  data as it can be used to optimise the painting code (instead of
  checking each room in an area to see whether(2D map) or when (3D) it
  needs to be drawn based on checking its z-coordinate, having lists
  already to hand must make things faster)...

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1383998/+subscriptions