mudlet-makers team mailing list archive
-
mudlet-makers team
-
Mailing list archive
-
Message #04914
[Bug 1658271] Re: Debug console does not indicate from which profile a message came from
Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/804
This issue needs to be closed and there is no appropriate status, so
will set it to "Opinion" just for migration purposes.
** Bug watch added: github.com/Mudlet/Mudlet/issues #804
https://github.com/Mudlet/Mudlet/issues/804
** Changed in: mudlet
Status: New => Opinion
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1658271
Title:
Debug console does not indicate from which profile a message came from
Status in Mudlet:
Opinion
Bug description:
To enable debugging of some potential errors when loading a profile I
had one already open with the "Central Debug Console" visible before
connecting to the second profile - I then realised that it was
impossible to see which profile was the source of any of the text
being shown in that window. We need to include the profile name (or
perhaps the Host ID number would do at a push) when more than one
profile is active.
Note that assuming this detail is placed after the time stamp then the
code that paints on or retrieves the data from this TConsole instance
allows for the extra characters (which if we use a number rather than
the name can be kept to a minimum). Changing from single to multi-
playing mode or a change in the total number of active profiles could
perhaps include a message saying which profile is which number (or for
the return to a single profile just which one it represents) which may
be useful if the text is copied for a log of a situation. It would
probably also be a good point to introduce code that enabled or
disabled (or even hide) the "MultiView" button on the Main Toolbar
which would also want to be tied into the monitor for the number of
profiles. It is not entirely clear what effect the "DefaultHost"
TConsole will have on this given that it is the owner of the Central
Debug Console and in some views appears to be an active profile (at
least as far as the HostManager class goes...?)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1658271/+subscriptions
References