mudlet-makers team mailing list archive

[Stephen Lyons <1163444@xxxxxxxxxxxxxxxxxx>]

If this is the same Room Exits GUI that has Text Line edit boxes for
normal directional exits and buttons for each that "Lock" to prevent
*editing* those same Text Line edit boxes at the same time as they set
the feature to prevent the route finding code from using that exit - as
the API lockExit() function does then I may be able to assist.

Sorry if this is a bit dense:

I have made some progress working over the GUI dialogue box and associated code to draw all the exit control functions together:
* exit stubs and validated exit entry (also color coded to indicate validity as the digits are entered) - mutual exclusivity is enforced;
* exit locking and spin-boxes (0-9999) for exit weighting {though given that a locked exit is effectively an infinite room weighting we could code the former as a -1 value to the latter}
* radio buttons to set/clear door markers
* a centrally place indicator to show the number of the room that is being EDITed!
* tool-tips to guide the user + an a disabled, dummy copy of the controls for one exit enlarged to accommodate the labels that would otherwise be redundantly duplicated and make larger the controls for each exit.

I had enforced mutual exclusivity for the other controls with stub exits
but I realise that in practice one is perfectly likely to find a locked
door without knowing what is on the other side so the door marker
control at least should be enabled for either a stub exit OR a valid
exit.

In testing I have found that the 2DMap drawing code attempts to draw
stub/normal exits for the up/down/in/out directions but fails for the
latter pair to single centrally placed thin horizontal line - I've hand
bodged the code to draw a small (about 2/3rd the size) pair of inward
pointing triangle for "in" that sits in the space left and right of the
points of the "up" and "down" exit indicators and a slightly larger
outward pointing pair on the outside of these for "out".  They, like the
"up"/"down" pair are hollow for stubs and filled in for real exits.  May
I suggest that someone a bit better at the coordinate number juggling
looks that bit of code over - what I propose is only a suggestion but it
visually "fits".

I also had left out controls for door symbols for the
"up"/"down"/"in"/"out" but I had subsequently thought that we could
change the brush colour used to "fill-in" the symbols to match the
colours used for the xy-plane ones - retaining the black outline though
so that they still show up on any room that has its environment set to a
colour that matches one of the door colours.  Humm, that would not work
for a stub exit with a marker door though ...

I've held off on further tweaking here as Heiko suggests there is some
revision to the mapper coming through shortly but I think there are some
more things that need work: the Special exit part - needs another column
for exit weighting the special exits, unless we combine it with the exit
locking.  Do we need the ability to set door symbols on exits drawn with
custom exit lines, could put the marker on the first line from the room,
in which case we can add them also to Special Exits.

OK that's enough from me for the moment.

** Attachment added: "Replacement Exit Dialogue box - work so far"
   https://bugs.launchpad.net/mudlet/+bug/1163444/+attachment/3616553/+files/Screenshot-Exit%20details%20for%20room.png

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

Title:
  Mapper GUI doesn't match API functionality

Status in Mudlet the MUD client:
  New

Bug description:
  The API method setExit() will automatically remove exit stubs from a
  room for the directions being set. However, if a user uses the Mapper
  window GUI (via right-click->exits), the exit stubs are not correctly
  removed.

  Ideally, the Mapper GUI would honor the setExit() behavior as there is
  no GUI-accessible way to remove exit stubs otherwise short of deleting
  the room.

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