Public bug reported:
Although the related https://bugs.launchpad.net/mudlet/+bug/1413069 has
been fixed I noted in that we still need to provide error messages for
the process - there are several places in Host::installPackage() and
related code where debugging code or comments indicate where
** Changed in: mudlet
Status: New => Confirmed
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1632854
Title:
Renaming an area doesn't update it on the "Info" mapper label
Status in Mudlet:
I think they'll realise it when the package doesn't get installed.
On Mon, Dec 19, 2016 at 4:55 PM Stephen Lyons
wrote:
> The release_30 version https://github.com/Mudlet/Mudlet/pull/360 has
> been merged into the codebase - so the unpacking should no longer stall
> -
The Lua setAreaName() command just needs to call the code to update the
2-D mapper - there are one or two other commands that can influence the
mapper display that also need this tweak (or an equivalent one that
updates both 2- and 3-D mappers). As it only needs to be done if a map
is present
Whilst this was an element of
https://bugs.launchpad.net/mudlet/+bug/1254364 the latter is not IMHO a
duplicate of this bug and so I have undone that linkage.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
The release_30 version https://github.com/Mudlet/Mudlet/pull/360 has
been merged into the codebase - so the unpacking should no longer stall
- again I remark that the code is still greatly under-equipped with
error handling messages so that the user may not realised that something
has failed even
As we have added messages to the screen at the beginning and end of map
file loading and have made progress with the "Unpacking module/package"
widget that pops up whilst modules/packages are being installed into a
profile I believe this is less of an issue now.
I do have a suspicion that the
7 matches
Mail list logo