mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Okay - how do you think we should get the fix into release_30 though?
Cherrypicking... doesn't do what it says in the manual, it tries to pull
across more changes than just that one commit you made on development. I
guess our only option is to manually copy the changes across? I'm happy to
do that, just deciding on the best option here.

On Mon, Mar 20, 2017 at 2:45 PM Stephen Lyons <slysven@xxxxxxxxxxxxxxx>
wrote:

> Well, if the "Map Auditing" went into the release_30 then I think the
> bugged data (custom line data items in the TRoom class with a empty
> string as the "key" in the various structures) should get cleared out
> when reloaded if it does get saved. Worth checking to see whether such a
> line created can be selected AND deleted from the 2D map GUI - which
> would make it an annoyance or whether it provokes a crash - which would
> make it a more serious problem...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1369041
>
> Title:
>   Custom exit lines - closing the dialog via 'X' creates some kind of an
>   exits line
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mudlet/+bug/1369041/+subscriptions
>

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

Title:
  Custom exit lines - closing the dialog via 'X' creates some kind of an
  exits line

Status in Mudlet:
  Confirmed

Bug description:
  Right-click on a room, select 'Custom exit lines', then hit the X (not
  Cancel) to close the dialog. Right-click on the room again and the
  menu to finish a custom exit line will show - when none was being
  created.

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