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()
Currently each two way exit line is drawn twice for rooms in the same
area, with the effect that unless you set a door symbol on both ends of
the exit the square that is drawn appears to be underneath the exit line
for some exits (where the symbol is on the first room that draws the
exit line) and
** Attachment removed: Exit lines being drawn both under and on-top of door
symbols
https://bugs.launchpad.net/mudlet/+bug/1164804/+attachment/3622338/+files/Exit%20lines%20being%20drawn%20twice
** Attachment added: Examples of door symbols sometimes on-top and some times
under exit lines
Yes, the exit option that Saves any changes only allows an exit stub
to set if there is NOT a valid exit room ID and the check box for a stub
IS set - but I'm going to review and incorporate Heiko's update before I
do anything else.
--
You received this bug notification because you are a member
The bottom line here is that visually a line leaving a room horizontally
to the right might appear to be an east exit but it could be actually
any (well certainly an orthogonal - n, ne, e, se, s, sw, w or nw) one
and you would not be any the wiser until you tried using it or examined
the room
One (extensive) thought: You could draw a stub in the correct direction for
orthogonal for ANY exit in the x-y plane being considered and put a (colored to
represent door type like wot I dun) door marker as appropriate then:
A) For a stub exit: do nothing more;
B) For a normal route:
IF a
Public bug reported:
A mistake in line 63 of the current src/TRoom.h assigns a new west exit
to a room to the southwest position rather than the west one, also
making it impossible to remove a west exit. The fix is trivial to
correct I think :
diff a/src/TRoom.h b/src/TRoom.h
--- a/src/TRoom.h
Public bug reported:
Current (660) revision:
Whilst researching for other TLuaInterpreter methods that were subject
to the zero'th index problem mentioned in
https://bugs.launchpad.net/mudlet/+bug/1173407 I discovered that
TArea::getRoomsByPostion() was reporting rooms in ALL areas with the
A quick check suggests that the following Lua functions (ie in
TLuaInterpreter.cpp) use an index that starts at zero and that the index is
directly returned as a key thereby creating a table with keys including
zero - I had wondered why some lua display(somefunction()) had produced
Does not seem to for me on the same code I think. I note that the line-
making part seems to be initiated as soon as one hits the exit selection
buttons in the case of lines for normal exits - given that these are at
the top of the dialogue a user unfamiliar could wonder where the
dialogue box
On 15/08/13 22:39, Vadim Peretokin wrote:
I was going to discard this idea after Heiko mentioned aliases which is a
very valid point, but Chris' idea saved it. Allowing people to set the
autocorrection words themselves is the way to go.
Can I also my 2 eurocents worth and add the warning that
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven)
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1096843
Title:
Doors should be configurable via UI
Status in Mudlet
Actually that is not quite correct - a comprehensive backup policy which
aims to optimise for security of data AND for non-infinite backup media
space will use a combination of differential and full backups -
balancing the ratio and frequency of each to fit the requirements. Not
everyone is using
On 17/09/13 23:59, Vadim Peretokin wrote:
Yeah I agree. We should be able to create rooms, not have to place them
into an area - setup their properties and then add it to one.
Ah, I recently was adding some rooms to an old map to test some
mapping code. I had an empty area and although
Just a thought - there is no chance of a circular exit in the (special
or otherwise) exits of the room being deleted? I.e. an exit that links
to the same room, it CAN happen in some MUDs and should be carefully
handled (or actually skipped) so you don't try to change the exit for
the room at the
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
How did you centerview() on a room that is not valid? Do you mean
that it was created with addRoom() but not assigned to an area with
setRoomArea(roomID, area_to_assign_room_to_ID)?
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
Ah, one of those patches I sent you Heiko overhauls the room exit
dialogue though I don't think it'll be hit by anything that revises the
TArea code.
I notice from the recent git master branch that setting a normal room's
area to 0 seems to be permitted by the lua code but it really messes
things
I think this may get a bit esoteric but *is* it OK for
TRoomDB::getRoom() to return the int value zero as a return value of
type TRoom * and then for that return value to be used as a boolean
logical value in TLuaInterpreter::centerview()? I started looking it up
and got very confused... 8-o
On
It was stupidly late for me to be thinking about code! But what was
unclear to me is: whether - as part of the code used for
TLuaInterpreter::centerview() where it calls TRoomDB::getRoom() and uses
the return value as a boolean one as part of an if() condition. In the
case I was unsure about I
The thing about area 0 seems to be we don't seem to actually explicitly
create it! Also the code to move rooms to an area does not seem to
update the old area to take the room FROM it - we get away with this at
mostly at the moment because I guess the typical usage is to create a
room and then
I think I may have caught this one already! 8-)
I had already submitted a commit to Heiko (file: commit-a919f07, sent
20/08/2013) which propagates a version string defined in the project
file to the various places where the Mudlet version is required or is
useful. Typically this is of the form
On 28/09/13 00:50, Vadim Peretokin wrote:
On Sat, Sep 28, 2013 at 3:53 AM, Stephen Lyons
1226...@bugs.launchpad.netwrote:
The thing about area 0 seems to be we don't seem to actually explicitly
create it! Also the code to move rooms to an area does not seem to
update the old area to take
Gosh there ARE some issues with this map:
Over 2000 Lost rooms - not in any area's rooms list.
Areas with an id of -1 or 0 - which some parts of the code will barf on...
A number of rooms that appear in the rooms list of more than ONE area.
A room with an id of 0.
Areas that have an Id number but
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven)
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1238339
Title:
changing room area doeas not remove it from previous area rooms
with which it can be remade from other data within the same map file
should make that a minor issue.
** Affects: mudlet
Importance: Medium
Assignee: Stephen Lyons (slysven)
Status: New
** Patch added: Patch to current code to correct bug.
https://bugs.launchpad.net/bugs/1248806
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I note that Debian is retain the use of Qt4 Libraries (including Phonon)
rather than the new Qt5 which may be an issue for the current Mudlet 3.0
release candidates...
On 11/11/2013 00:05, Travis Johnson wrote:
unfortunately it looks like it isn't
Just checking something else and found that the custom_lines.ui file has
been improved (I think it was suggested that all the exits should be
listed in a table for the user to select one from) and all the push
buttons for the normal exits have been removed (by Heiko in commit
f30a55).
I agree. For example, that sample map with problems takes a LONG time
to load and if I didn't have the QT Creator IDE application output
displaying stuff I'd be wondering what was happening just during the map
restoration part involving that map (and even then the 40K room
wilderness area
Yes - but I forget/was unable to amend the MAC project file, though I
hope the change to the normal one will be sufficient if copied across.
Examining the patch I made it is not clear that the modified Splash
image (with the version text removed from the image) is included...
On 25/11/13 05:27,
Actually, as a fix for the [0] issue, why not provide, e.g. a
getExitStubs1() - note the '1' suffix - for those few messed up cases
and correct the index issue in them. Going forward we can document
these case and direct new users to them, pointing out way we haven't
changed the originals to
Public bug reported:
I was getting fed up during debugging area and map code that I kept
getting segmentation faults in the A* route finder if I clicked on rooms
during usage of the 2D Map GUI. It turns out that this is caused if
there are no (usable) exits from the start room for route finding
@Chris:
I think we were working in parallel, I'd not been on-line during heavy
coding sessions over past few days and wasn't aware of
https://bugs.launchpad.net/bugs/1263447, I was just getting fed up with
segFaults that I couldn't back out of during debugging - what is it they
say about great
Public bug reported:
This relates to but is independent of #1248806 {fast_
ausgaengeBestimmen() don't store TO roomID}. I think that another pair
of eyeballs would help but as the summary says, when we delete a room
we'll need to make sure that if it is the END of an inter-area link (as
should
There may be merit in holding onto the results from
TArea::koordinatesystem() within the in-memory TArea - I experimented
with this and swapping the z and x coordinates (so the z one was the
outermost one) - although it made room movement more complex (especially
if the z coordinate was changed) I
Humm, I know very little about MXP but I was looking through
http://www.zuggsoft.com/zmud/mxp.htm to try and get my head around this
and my first though is that # is a reserved character in (HTTP:) URIs
see http://tools.ietf.org/html/rfc3986#section-2.2 (- note the use here
of # and you might see
Public bug reported:
The current LUA interface to the user room data is very limited.
Knowledge of the key is required to use getRoomUserData(). Also, it is
not possible to remove a specific key-value tuple from the user data
even if one does know the key to use - a workaround to use the
I understand, and not wishing to put anything libellous, it does seem
that Zugg has created specifications that do have some areas of, how
shall I put it, *uncertainty*...:
http://www.mudbytes.net/index.php?a=topict=3808
--
You received this bug notification because you are a member of Mudlet
** Patch removed: Improve LUA acces to room user data
https://bugs.launchpad.net/mudlet/+bug/1275255/+attachment/3965347/+files/commit-967e912
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
Ah, that seems a bit more elegant, will do...
I'll leave the previous patch up - it got quite involved in learning how
to manipulating my local repo to stash everything, rewind, recreate a
combined patch and then unwind again - and I'm not madly keen to do it
again so soon as I think I nearly
I'm now happy with my fix/enhancement to custom lines stuff which is
waiting for peer review(?) into Chris7/Mudlet2/mudletDev and then
propagation upstream.
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven)
** Changed in: mudlet
Status: Confirmed = In Progress
As part of putting together something to centralise Mudlet version
information I needed to add a basic command line argument handler (to
provide FSF's recommended --help and --version handling) that is
awaiting peer review at GH's Chris7/Mudlet2/mudletDev (see my
Code awaiting peer review (pull request #30 into GH
Chris7/Mudlet2/mudletDev).
** Changed in: mudlet
Status: New = In Progress
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1096843
Title:
mudletDev_proposedUpdates branch.
On 07/04/14 03:34, Vadim Peretokin wrote:
Hm the link is a 404, what do you also mean by fake auto-logins?
On Mon, Apr 7, 2014 at 12:17 PM, Stephen Lyons
760...@bugs.launchpad.netwrote:
As part of putting together something to centralise Mudlet version
information I needed
Is this a duplicate of #1091056?
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1091056
Title:
Reset map colors to default button doesn't work
Status in Mudlet the MUD client:
In Progress
Bug
There is a bit of a dichotomy with the way that exit directions are
treated but in the long term I think we may have to split exit
directions into two groups, the normal exits which we can represent
with a (short unsigned) numeric constant internally and special exits
with a string representation.
Is this a duplicate of #1091056?
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1093377
Title:
Settings dialog doesn't set default colors properly.
Status in Mudlet the MUD client:
New
Bug
Blast, got my branches confused I MEANT TO SAY my
mudletDev_fixGSysMessage branch at
https://github.com/SlySven/Mudlet2/tree/mudletDev_fixGSysMessage. And
this is the same output from it.
** Attachment added: Proposed, fixed display
Note that there was an issue in that the error strings from the lua
interpreter started some lines with a tab character which was messing up
the pre-fix display (text was spilling over onto colored background part
of screen). The pre-fix shot shows both an Error message and an OK one
for the lfs
Public bug reported:
In https://bugs.launchpad.net/mudlet/+bug/1310361 I investigated an
issue that revealed a further matter that I am not skilled enough to
fix. If more than one required external module is missing the part of
the error messages that are shown that come from the lua interpreter
for the stack.
On Mon, Apr 21, 2014 at 6:07 AM, Stephen Lyons
1310...@bugs.launchpad.netwrote:
Public bug reported:
In https://bugs.launchpad.net/mudlet/+bug/1310361 I investigated an
issue that revealed a further matter that I am not skilled enough to
fix. If more than one required
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven)
** Changed in: mudlet
Status: New = In Progress
** Changed in: mudlet
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed
** Changed in: mudlet
Status: New = In Progress
** Changed in: mudlet
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1310361
Title:
Global gSysMessage
As I reported in my contributions to that forum thread the code of
TLuaInterpreter::getHomeDir() will be mangling what M$ Windoze now
permits to be used for User names. It is not yet clear to me at what
point that operating system allowed user-names and thus the user
directories that are created
** Changed in: mudlet
Assignee: (unassigned) = Chris (chrismudlet)
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1329948
Title:
rightclicking the left aligned timestamp frame crashes the
Chris
Sorry if I've dropped it onto to you a bit abruptly but can you get this
two line patch up into the current SF release?
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1329948
Title:
I'm getting some mojibake (after the processTelnetCommand: in lines
containing that and also at the end of the same lines) when viewing
posting: Vadim Peretokin (vperetokin) wrote on 2013-09-29. Maybe its
not an issue but just the side effect of cut and pasting raw telnet byte
sequences with
I was wrong it does involve switching between all the tabs...
Can you give me a pointer to the Fix (where is it committed?) or patch?
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1269582
Title:
Use the Editor to work on a script for an Alias/Script or Trigger, take
a copy of the contents of the working area on the right (e.g. under all
the trigger settings stuff on THAT tab) so that you can replace them.
Now click on one of the other tabs (originally I thought it was just the
variable
Public bug reported:
Just checking the vyzor.mpackage file that is included in the source
code and EMBEDDED into the Mudlet executable via the resource file I
find it contains files the latest of which has a date-stamp of 30
November 2012! Given that at the time of writing Oneymus's latest
This is caused by a missing else in dlgTriggerEditor::saveAlias() (in
around line 3639 of dlgTriggerEditor.cpp) which means that the grey
(disabled by ancestor) icon is used. It is fixed in code put forward my
me and currently being checked over by Ahmed Charles in his GH
repository, branch
other things
that could be more standards compliant.
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven)
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1130450
Title:
Copy
** Changed in: mudlet
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1201017
Title:
Custom exit lines dialog broken in git
Status in Mudlet the MUD
** Changed in: mudlet
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1310372
Title:
Start-up error messages from Lua interpreter only show first error
** Changed in: mudlet
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1310361
Title:
Global gSysMessage leaks messages between profiles
Status in Mudlet
** Changed in: mudlet
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1232576
Title:
Mudlet still identifies itself as Mudlet 2.0.1 in ATCP
Status in
** Changed in: mudlet
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1096843
Title:
Doors should be configurable via UI
Status in Mudlet the MUD client:
** Tags added: map
** Tags removed: map
** Tags added: mapper-2d
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1097514
Title:
Doors aren't drawn on custom exit lines
Status in Mudlet the MUD
** 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/1154978
Title:
Search and other buttons go black
Status in Mudlet the MUD client:
Confirmed
** Tags added: mapper-3d
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1100475
Title:
Up exits in 3D mode under certain angle are difficult to spot
Status in Mudlet the MUD client:
New
Bug
May also want to consider /usr/local/share/hunspell also, though I can't
imagine a distribution based Linux system NOT having hunspell or some
other packaged spellchecker so the need for a local (admin) build seems
unlikely...
--
You received this bug notification because you are a member of
So either Mudlet/major version number.minor version number or
Mozilla/5.0 (Mudlet/major version number.minor version number)
with major version number and minor version number parsed from the
APP_VERSION #define. Then hope that we don't break it for other users
who have gotten away with
Ah, right, well I'll code in Mudlet/major.minor then.
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven)
** Changed in: mudlet
Importance: Undecided = Low
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet
Can we have a little more context please...?
** Changed in: mudlet
Status: New = Incomplete
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1369186
Title:
Z axis adjustment of elements
I've been tempted to see whether we could add a context menu to map
labels to allow their properties to be tweaked - like you can/soon will
be able to do for exit custom lines and exits, a spin box to set the z
coordinate (and something for the above/below map display) seems likely
additions...
It still seems to be using the 16x16 icon (set in the mudlet Class
constructor), I'd changed it somewhere to 48x48 which is a bit better
but that got bogged down in other UI changing stuff.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to
Is this still an issue, IIRC there have been changes in the exits area
of the code which may have impacted on this?
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1226481
Title:
deleteArea()
20:08, Vadim Peretokin wrote:
It is being rewritten, it should be a 'W' and was a 'W' in 2.1.
On Mon, Sep 22, 2014 at 11:46 PM, Stephen Lyons 1369...@bugs.launchpad.net
wrote:
The odd character here is coming up as Unicode point U+2592 MEDIUM
SHADE - in Utf-8 that would be the three byte
Ah, for me too. In the cTelnet destructor, just after (not as a result
OF) it using some abnormal exit handling stuff I put in a while ago to
display previously un-displayed messages before an abnormal application
close. Seems to be something about deleting a scoped pointer, so I'm
wondering
Ah, so one of the errant bytes is a 0xFF - well THAT is Telnet IAC
followed by 0xC9 (decimal 201 ???) which corresponds to GMCP doesn't it?
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1369505
I would like to work on this proposal - I have some ideas as to how we
can leverage it into existing code-base.
** Changed in: mudlet
Status: New = Incomplete
** Changed in: mudlet
Status: Incomplete = Invalid
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons
** Changed in: mudlet
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1130450
Title:
Copy to HTML uses an invalid font-decoration property
Status in Mudlet
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven)
** Changed in: mudlet
Status: Confirmed = In Progress
** Changed in: mudlet
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed
Ah, lose the .data() bit from that last line... - other tweaks could
be necessary further down main() to access app's methods and members!
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1375447
Is the change to use a QScopedPointer compatible with the qobject_cast()
used to convert the pointer returned from createApplication() which can
be EITHER a QCoreApplication (for the case where a commandline -h(elp)
or -v(ersion) argument is used and a GUI application is NOT to be
created) OR a
** Changed in: mudlet
Status: Confirmed = Fix Committed
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven)
** Changed in: mudlet
Importance: Low = High
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed
** Changed in: mudlet
Status: New = In Progress
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven)
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1375449
Title
I need to know: does Qt on Windows use '-' or '/' as a command line
argument prefix, when I did the parser for it I coded it to respond to
'/' but further reading suggests that actually '-' is used.
To check: can someone start up a cmd.exe console and try running Mudlet
from there with first
Does the code execution go as expected using '/help' '/?' or '/version'
if you step through the code - is it getting to the relevant couts and
those are not producing any output or is it not even getting to them
there?
--
You received this bug notification because you are a member of Mudlet
Would Chris be able to provide some hints on my queries if we asked
nicely?
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1375449
Title:
Command-line options on Windows don't seem to work
Status
** 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/1369040
Title:
Room exits dialog room # tooltip is coloured
Status in Mudlet the MUD client:
Public bug reported:
I was noting repeated: QIODevice::write: device not open Application
output messages when using the Connection Profiles Dialog and any of the
Predefined MUD icons were selected that I had never actually connected
to - this includes the very first one that is the default when
** Summary changed:
- Broken program logic in dlgConnectionProfiles dialog: assumes profile
directory exists when not gaurenteed for predefined MUD ones
+ Broken program logic in dlgConnectionProfiles dialog: assumes profile
directory exists when this is not guaranteed for predefined MUD ones
Ah, is a typo in two places, the CSS is font-style: italic; NOT
italics.
Will roll this up into fix for underlines.
https://bugs.launchpad.net/mudlet/+bug/1130450
** Changed in: mudlet
Status: New = In Progress
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven
Fix in Pull Request: https://github.com/Mudlet/Mudlet/pull/206
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1130450
Title:
Copy to HTML uses an invalid font-decoration property
Status in Mudlet
Fix in Pull Request: https://github.com/Mudlet/Mudlet/pull/206
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1102360
Title:
Italics don't get logged
Status in Mudlet the MUD client:
In
Confirmed, should be able to fix by wiring-up the dialog's close
button to the Cancel one...
** Changed in: mudlet
Status: New = Confirmed
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven)
** Changed in: mudlet
Importance: Undecided = Medium
** Changed
Fix proposed: https://github.com/Mudlet/Mudlet/pull/215
--
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
** Changed in: mudlet
Assignee: (unassigned) = Stephen Lyons (slysven)
** Changed in: mudlet
Importance: Undecided = Medium
** Changed in: mudlet
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed
It is caused by the Cascading nature of the CSS that Qt is emulating -
by default using the setStyleSheet() method on the line edits used to
hold the exit to room id numbers to colour them is being carried down to
their child elements which includes the tooltips. I have found the fix
is to be
1 - 100 of 304 matches
Mail list logo
