No, the exit drawing code for *custom lines* isn't agnostic about directions and does exactly what daagar is after imho - if I understand him correctly.
Am 08.04.2013 18:30, schrieb Stephen Lyons: > The 2D map drawing is actually agnostic about the "name" or command for > orthogonal exits which means that implementing code that would, say, > draw half a line in the right direction for the exits for each room such > that they would line up for two adjacent rooms in the right physical > placement and then link the end of those lines if they are NOT in > adjacent correct positions means more than a trivial revision to the > (rev 658) code. :( > > I'm just reviewing 659 so can't comment on that yet. > -- 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 _______________________________________________ Mailing list: https://launchpad.net/~mudlet-makers Post to : [email protected] Unsubscribe : https://launchpad.net/~mudlet-makers More help : https://help.launchpad.net/ListHelp
