mudlet-makers team mailing list archive

[Stephen Lyons <1164804@xxxxxxxxxxxxxxxxxx>]

One (extensive) thought: You could draw a stub in the correct direction for orthogonal for ANY exit in the x-y plane being considered and put a (colored to represent door type like "wot I dun") door marker as appropriate then:
A) For a stub exit: do nothing more;
B) For a normal route:
    IF a reverse path is also present to the first room AND returns from the opposite room THEN
        draw a straight line from the end of the stub to the corresponding stub on the other room
        (takes care of say an "east" route that goes to another room whether the reverse path is say "north" as well as when the the reverse route would be "west"; also takes care if the second room IS NOT due "east" in a coordinate sense.)
    ELSE
        draw a straight line from the end of the stub to the center of the other room.
For the trivial case where the two rooms are adjacent and at "unity" spacing from each other, if the stubs are drawn to the point that is half way between them no addition line is required to be drawn.
C) For a one-directional route drawn a triangular direction arrow on the start of the line from the exit stub to the center of the "to" room - so would look pretty much the same as now.
D) For a route "out-of-area" extend the stub to the full distance that an adjacent room would occupy - allowing space for the one-direction arrow if needed as the start of the extension then do the thick arrowhead we do at present on the end of the line.

Also, this could work for the custom lines as well if they were started
from the end of the corresponding stub - would allow them to support
door markers too.  It might be nice if we could have them snap to the
centre of rooms OR to the ends of the exit stubs if they are within a
certain distance of such things - and then the last segment of a multi-
segment line could track the room that it connects to as non-custom ones
do?

Finally, it might be possible to fit in additional stubs around the room
symbol for the "in", "out", "up" and "down" exits so that people who
draw area maps all on one x-y plain could actually show the linkages for
those as well - and for up and down exits if rooms are more than one z
unit apart there could be "adapters" to mate with the "down" exit from a
room above or "up" from below, draw them into the center line of the
room they come from (i.e. int(x), int(y)) so that further z values away
can show a circular mark for the vertical paths (or an ellipse in the
appropriate direction if an x and/or y offset is needed) when viewing
areas with rooms off the current z value.

P.S.
I should perhaps indicate that I'm an Electronics Engineer by training and some of my thoughts are coming from a Printed Circuit Board CAD point of view (I'm seeing similarities with moving rooms in the X-Y plane and "rubber-banding" of components on a circuit board where components and copper tracks are moved but retain connectivity; also vertical routes here and "vias" between different layers on a "multi-layer" circuit board....)

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

Title:
  Exit lines don't 'anchor' to exit direction

Status in Mudlet the MUD client:
  Invalid

Bug description:
  Mudlet 2.1, Win7 x64

  Visual issue in the mapper:

  Consider two rooms connected east-west. If I move the room to the east
  'below' the room to the west, I would expect the connection between
  them to visually be a 'Z' shape, where it is obvious that the exits
  still extend from the east and west respectively.

  Instead, the lines originate from the center of a room. So if I move
  the east-west pair as above, the exit line will visually appear as if
  it extends from the south/north.

  The exit lines should potentially be drawn between the ends of the
  'exit stubs', rather from the center of a room. In the example above,
  this would give the expected 'Z' shape.

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