mudlet-makers team mailing list archive

[Stephen Lyons <1229493@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Running my development version based on current repository I noticed
that if I ran multiple sessions and used the built-in mapper (not geyser
one) and closed a session by clicking the close button on the tab the
corresponding mapper was not removed.  On restarting the profile
(without closing the other session(s)/mudlet itself) a new built-in
mapper was successfully created - the original one was still functional
(at least as far as changing exits and moving rooms within area) but
changes in its data were not saved when I eventually did exit that
instance of mudlet.

This'll need checking in a "proper" version but I suspect the same will
apply, a fix must ensure closing the profile closes the matching mapper
if the built-in one is in use - I guess a geyser one would be closed
down but I don't know that.

Reason why I use the built-in one: I can drag it (the dock widget that
it is in) to a second monitor in a virtual (multi-monitor) display set-
up...

** Affects: mudlet
     Importance: Low
         Status: New

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

Title:
  Closing session console not closing built-in mapper in multiple
  sessions

Status in Mudlet the MUD client:
  New

Bug description:
  Running my development version based on current repository I noticed
  that if I ran multiple sessions and used the built-in mapper (not
  geyser one) and closed a session by clicking the close button on the
  tab the corresponding mapper was not removed.  On restarting the
  profile (without closing the other session(s)/mudlet itself) a new
  built-in mapper was successfully created - the original one was still
  functional (at least as far as changing exits and moving rooms within
  area) but changes in its data were not saved when I eventually did
  exit that instance of mudlet.

  This'll need checking in a "proper" version but I suspect the same
  will apply, a fix must ensure closing the profile closes the matching
  mapper if the built-in one is in use - I guess a geyser one would be
  closed down but I don't know that.

  Reason why I use the built-in one: I can drag it (the dock widget that
  it is in) to a second monitor in a virtual (multi-monitor) display
  set-up...

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