[Mudlet-makers] [Bug 1959465] Re: Mudlet not respecting user-selected server data encoding setting

[Vadim Peretokin]

Hi!

> When connecting to MUME with Force CHARSET negotiation enabled (box
NOT checked under Special settings)

There is no 'force charset negotiation on' option, just an option to
turn it off which is why I think you're confused.

The way it works is: you can either allow the server to set the
encoding, or you want to choose it yourself in which case you don't
allow it.

It's unfortunate that MUME is giving preference to ISO 8859-1 - it
should give preference to UTF-8.

I hope that helps!

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

Title:
  Mudlet not respecting user-selected server data encoding setting

Status in mudlet package in Ubuntu:
  New

Bug description:
  When connecting to MUME with Force CHARSET negotiation enabled (box
  NOT checked under Special settings), and UTF-8 selected for Server
  data encoding in general settings, encoding is changed to ISO 8859-1
  during negotiation with the server. It appears that, during this
  negotiation, the server offers several options, and Mudlet is choosing
  the first compatible option in the list (ISO 8859-1) rather than the
  user selected preference (UTF-8), which is also available.

  I was able to use UTF-8 by turning Force CHARSET negotiation off and
  manually setting UTF-8 in the MUD using the command line.

  I think the expected behavior (at least the behavior I expected) is
  that, if I have Force CHARSET negotiation on, and have chosen a
  particular encoding, Mudlet would enforce that encoding with the
  server, if it is available.

  Here are the packets that are exchanged during the negotiation:

  From Mud to MudletP:

     a8 a1 59 24 c5 05 60 5f 8d 05 ba f2 08 00 45 00   ..Y$..`_..E.
  0010   00 6f d3 f7 40 00 2f 06 13 5e c1 86 da 62 c0 a8   .o..@./..^...b..
  0020   07 a2 10 92 94 32 78 00 8c b4 7c ca 98 fc 80 18   .2x...|.
  0030   01 fc a2 12 00 00 01 01 08 0a d7 7b b5 a4 f1 35   ...{...5
  0040   5c a1 ff fa 18 01 ff f0 ff fa 2a 01 3b 49 53 4f   \.*.;ISO
  0050   5f 38 38 35 39 2d 31 3a 31 39 38 37 3b 49 53 4f   _8859-1:1987;ISO
  0060   2d 38 38 35 39 2d 31 3b 55 54 46 2d 38 3b 55 53   -8859-1;UTF-8;US
  0070   2d 41 53 43 49 49 ff f0 ff fa 56 ff f0-ASCIIV..

  Response to Mud from Mudlet:

     60 5f 8d 05 ba f2 a8 a1 59 24 c5 05 08 00 45 00   `_..Y$E.
  0010   00 57 1f 0b 40 00 40 06 b7 62 c0 a8 07 a2 c1 86   .W..@.@..b..
  0020   da 62 94 32 10 92 7c ca 98 fc 78 00 8c ef 80 18   .b.2..|...x.
  0030   01 f5 64 7d 00 00 01 01 08 0a f1 35 5d 93 d7 7b   ..d}...5]..{
  0040   b5 a4 ff fa 18 00 4d 75 64 6c 65 74 20 34 2e 31   ..Mudlet 4.1
  0050   34 2e 31 ff f0 ff fa 2a 02 49 53 4f 2d 38 38 35   4.1*.ISO-885
  0060   39 2d 31 ff f09-1..

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


___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1670586] Re: /usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

[Vadim Peretokin]

** Changed in: mudlet (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  
/usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

Status in Mudlet:
  Opinion
Status in mudlet package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mudlet.  This problem was most recently seen with package version 
1:3.0.0~delta-3, the problem page at 
https://errors.ubuntu.com/problem/59f70700f1cb39d4a932f21b51ef5172da315be4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1416787] Re: Mudlet 3.0 opens as fullscreen on Win7

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/802

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 #802
   https://github.com/Mudlet/Mudlet/issues/802

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

Title:
  Mudlet 3.0 opens as fullscreen on Win7

Status in Mudlet:
  Opinion

Bug description:
  It seems if you fullscreen Mudlet once, closing it then on any
  dimension will keep opening it as fullscreen. See included screencast
  for demo.

  This doesn't happen in 2.1.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1654739] Re: Script content lost when moving to a new/different folder

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/803

This issue needs to be closed and there is no appropriate status, so
will set it to "Opinion" just for migration purposes.

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

Title:
  Script content lost when moving to a new/different folder

Status in Mudlet:
  Opinion

Bug description:
  Version 3.0.0-iota, macOS Sierra (10.12.3)

  I had a script in one folder/group and decided to move it to another
  folder. The contents of the script did not appear in the editor, but I
  did notice that the script appeared to be working as intended. I saved
  the profile and restarted Mudlet and at that point, the script stopped
  functioning and the contents appear to be lost completely.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1678368] Re: /usr/games/mudlet:11:std::_Deque_iterator:std::_Deque_iterator:std::_Deque_iterator:std::deque:TTextEdit::highlight

[Vadim Peretokin]

Only happens on 2.1, no reports on 3.0.

** Changed in: mudlet (Ubuntu)
   Status: New => Invalid

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

Title:
  
/usr/games/mudlet:11:std::_Deque_iterator:std::_Deque_iterator:std::_Deque_iterator:std::deque:TTextEdit::highlight

Status in mudlet package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mudlet.  This problem was most recently seen with package version 
1:2.1-2build2, the problem page at 
https://errors.ubuntu.com/problem/d4818a7d12fc10e8a7a65e681249c2259cbbf526 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1416787] Re: Mudlet 3.0 opens as fullscreen on Win7

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/778

This issue needs to be closed and there is no appropriate status, so
will set it to "Opinion" just for migration purposes.

** Changed in: mudlet
   Status: New => Incomplete

** Changed in: mudlet
   Status: Incomplete => Opinion

** Bug watch added: github.com/Mudlet/Mudlet/issues #778
   https://github.com/Mudlet/Mudlet/issues/778

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

Title:
  Mudlet 3.0 opens as fullscreen on Win7

Status in Mudlet:
  Opinion

Bug description:
  It seems if you fullscreen Mudlet once, closing it then on any
  dimension will keep opening it as fullscreen. See included screencast
  for demo.

  This doesn't happen in 2.1.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1676955] Re: disconnect() calls a sysDisconnectEvent of it's own

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/778

This issue needs to be closed and there is no appropriate status, so
will set it to "Opinion" just for migration purposes.

** Changed in: mudlet
   Status: New => Opinion

** Bug watch added: github.com/Mudlet/Mudlet/issues #778
   https://github.com/Mudlet/Mudlet/issues/778

** Bug watch added: github.com/Mudlet/Mudlet/issues #821
   https://github.com/Mudlet/Mudlet/issues/821

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

Title:
  disconnect() calls a sysDisconnectEvent of it's own

Status in Mudlet:
  Opinion

Bug description:
  Sample Code:

  function doubleEcho()
cecho("\nThis will echo twice, but only if currently 
connected to the MUD when disconenct() is called")
  end

  registerAnonymousEventHandler("sysDisconnectionEvent","doubleEcho")

  disconnect()

  
  Explanation:

  sysDisconnectEvent is designed to let you know that the connection to
  the MUD has been terminated. However, regardless of whether there is a
  connection to the MUD, calling the disconnect() function raises
  sysDisconnectEvent. When connected to a MUD, this results in
  sysDisconnectEvent being called twice if you manually run a
  disconnect(). If the MUD disconnects you on the other hand, you only
  get one sysDisconnectEvent, as proper.

  Usually this is no problem. However, sometimes a function that is
  registered to sysDisconnectEvent will have issues if it is run twice.
  Other times you may not want said function to run unless already
  connected to the MUD when disconnect() is called.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1676955] Re: disconnect() calls a sysDisconnectEvent of it's own

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/821

This issue needs to be closed and there is no appropriate status, so
will set it to "Opinion" just for migration purposes.

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

Title:
  disconnect() calls a sysDisconnectEvent of it's own

Status in Mudlet:
  Opinion

Bug description:
  Sample Code:

  function doubleEcho()
cecho("\nThis will echo twice, but only if currently 
connected to the MUD when disconenct() is called")
  end

  registerAnonymousEventHandler("sysDisconnectionEvent","doubleEcho")

  disconnect()

  
  Explanation:

  sysDisconnectEvent is designed to let you know that the connection to
  the MUD has been terminated. However, regardless of whether there is a
  connection to the MUD, calling the disconnect() function raises
  sysDisconnectEvent. When connected to a MUD, this results in
  sysDisconnectEvent being called twice if you manually run a
  disconnect(). If the MUD disconnects you on the other hand, you only
  get one sysDisconnectEvent, as proper.

  Usually this is no problem. However, sometimes a function that is
  registered to sysDisconnectEvent will have issues if it is run twice.
  Other times you may not want said function to run unless already
  connected to the MUD when disconnect() is called.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1658271] Re: Debug console does not indicate from which profile a message came from

[Vadim Peretokin]

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1676748] Re: Special characters cause script loss(?)

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/816

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 #816
   https://github.com/Mudlet/Mudlet/issues/816

** 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/1676748

Title:
  Special characters cause script loss(?)

Status in Mudlet:
  Opinion

Bug description:
  Pharanyx - Today at 12:10 AM
  This is getting really frustrating. I wish I could pin down why it's 
happening.
  Mudlet has randomly decided that a whole bunch of scripts that I have been 
working on today no longer exist and just completely removed the code from 
them. It's happened to around a dozen, all scripts I've worked on this session.
  Lost almost an entire days work.
  Seriously. Goddamit.

  Belgarath - Today at 12:12 AM
  Are you using the latest 3.0?

  Pharanyx - Today at 12:12 AM
  Am using 3.0.1-dev

  Belgarath - Today at 12:13 AM
  So you compiled it yourself (how long ago)?

  Pharanyx - Today at 12:13 AM
  Yeah, looking through my script objects now, every single object that I've 
made changes to today is completely gone. The object still exists, it's just 
had the code removed.
  Compiled about 3/4 days ago.

  Belgarath - Today at 12:15 AM
  Hmm. I hope that doesn't mean the official 3.0 still has that bug.
  I'd suggest installing the official 3.0.

  Pharanyx - Today at 12:15 AM
  Not an option for me. Too much of my system relies on development branch.
  My entire system would simply not work if I went back to 3.0

  Belgarath - Today at 12:16 AM
  Hard to say whether or not the version you compiled came before the official 
release that (claims) to have already fixed the script deletion bug.

  Pharanyx - Today at 12:19 AM
  That's odd. Just loaded a profile from earlier today, where the code was 
present.
  Gone from that profile, too.

  Buck - Today at 1:29 AM
  @Jor that usually happens to me if I put in a special character somewhere
  @Pharanyx * even
  it gets saved literally, and when mudlet tries to load it the next time, it 
chokes

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1654739] Re: Script content lost when moving to a new/different folder

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/803

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 #803
   https://github.com/Mudlet/Mudlet/issues/803

** 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/1654739

Title:
  Script content lost when moving to a new/different folder

Status in Mudlet:
  Opinion

Bug description:
  Version 3.0.0-iota, macOS Sierra (10.12.3)

  I had a script in one folder/group and decided to move it to another
  folder. The contents of the script did not appear in the editor, but I
  did notice that the script appeared to be working as intended. I saved
  the profile and restarted Mudlet and at that point, the script stopped
  functioning and the contents appear to be lost completely.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1651049] Re: Few/no error messages on loading packages

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/799

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 #799
   https://github.com/Mudlet/Mudlet/issues/799

** 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/1651049

Title:
  Few/no error messages on loading packages

Status in Mudlet:
  Opinion

Bug description:
  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 error
  messages need to be generated. As this code is used in a number of
  different situations the error reporting will need to take that into
  account.

  Ideally this ought to make it into the 3.0 release, IMHO - so I reckon
  this should at least be rated "Medium" importance.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1665801] Re: Mapper room tracking via ATCP does not set the right area in the area dropdown list

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/805

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 #805
   https://github.com/Mudlet/Mudlet/issues/805

** 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/1665801

Title:
  Mapper room tracking via ATCP does not set the right area in the area
  dropdown list

Status in Mudlet:
  Opinion

Bug description:
  This is due to
  https://github.com/Mudlet/Mudlet/blob/release_30/src/ctelnet.cpp#L1118
  not doing anything about it.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1645064] Re: Windows sound crash

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/798

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 #798
   https://github.com/Mudlet/Mudlet/issues/798

** 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/1645064

Title:
  Windows sound crash

Status in Mudlet:
  Opinion

Bug description:
  I've just started layering up sounds using windows / 3.0 epsilon

  If 5 unique sounds are attempted to be played simultaneously, mudlet
  locks up and crashes. The 2.1 wiki had mentioned that the limit on
  sounds was 4 at once - Being that's many versions ago, and more
  importantly a much older version of Qt, i'm not sure what the actual
  limit now -should- be. However, crashing isn't the right way to go
  about hitting the limit.

  I don't know if this is windows specific or not.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1671978] Re: Variables Data in Profile save file located and read after Lua code that may use them is compiled

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/807

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 #807
   https://github.com/Mudlet/Mudlet/issues/807

** 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/1671978

Title:
  Variables Data in Profile save file located and read after Lua code
  that may use them is compiled

Status in Mudlet:
  Opinion

Bug description:
  The ... element of the XML file
  data used to store the profile data between session is located and
  thus parsed AFTER the other members which contain Lua script elements
  that may require the variables that are contained within (the ones in
  a session that the user has marked as to be "Saved" between sessions).
  This effect may be (erroneously) masked by code that checks for and
  initialises such variables if it is *executed* before the real
  variable is read from the file, but perhaps NOT if it is just
  *compiled* {by which I mean the compilation system examines the code
  to deduce what data storage is required} in that case the absence of
  the required variable will just trigger a Lua syntax error about using
  a non-existent (nil) global variable - which would show up as a bug
  initially but disappear after the real variable is read.

  However in simple experimenting which attempted to save and thus load
  the variables BEFORE the other elements of a Mudlet profile - which
  will be the method to correct this - I encountered an odd error which
  I could not determine the cause of.  In that situation, installed
  packages would fail to show up in the Editor.  The package manager
  confirmed the presence of the packages but they never seemed to be
  loaded from the save file, even though a manual inspection showed them
  present in the file.  Note that this refers to packages, in both a
  single/group of one type of aliases and scripts and presumably (but
  not checked) buttons/menu/items, keys, timers or triggers, NOT
  modules.

  Although the presentation is very like
  https://bugs.launchpad.net/mudlet/+bug/1668177 {"Default packages are
  no longer installed on new profiles (temporary post-iota only)"} that
  was caused by single line of code in an `else` branch that had been
  placed in the wrong `if` of a nested 'if' - which does not seem to be
  the case here - though the mechanism that is invoked could be the
  same.  It is almost as some sub-system has been correctly set up in
  the case with the variables being loaded last but which has not been
  initialised before they are. This suggests some part of the variable
  store which interacts with the Lua subsystem but I have not been able
  to pin down the cause.

  Note that after a profile has been loaded once, variables and compiled
  functions persist in the Lua system I think; so if a profile is
  reloaded there is likely to be wanted variables/functions
  still/already in the system and thus the odd effects and problems are
  only likely to show up during session start-up.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1673240] Re: No obvious way to set LUA_DEFAULT_DIR

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/809

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 #809
   https://github.com/Mudlet/Mudlet/issues/809

** 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/1673240

Title:
  No obvious way to set LUA_DEFAULT_DIR

Status in Mudlet:
  Opinion

Bug description:
  My understanding of
  
https://github.com/Mudlet/Mudlet/commit/ee487888f219567635fb8334d980fd3fedd1f609
  was that you could pass LUA_DEFAULT_DIR the location of the installed
  Lua files at package creation time, but it does not seem to be the
  case? It seems you have to actually hack the source files - just like
  you had to before - if you'd like to use a different directory...

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1642262] Re: Crash when attempting a SQL select

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/797

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 #797
   https://github.com/Mudlet/Mudlet/issues/797

** 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/1642262

Title:
  Crash when attempting a SQL select

Status in Mudlet:
  Opinion

Bug description:
  Mudlet (Iota) crashes on the windows build, at least, as soon as a SQL
  select is issued. This is coming from the linked libraries.

  The below needs to be changed in mudlet's src.pro

  src.pro:

  } else:win32: {
  LIBS += -L"C:\\mudlet5_package" \
  -L"C:\\mingw32\\lib" \
  -L"C:\\mingw32\\bin" \
  -llua51 \
  -lpcre-1 \
  -llibhunspell-1.4 \
  -lzip \ # for dlgPackageExporter
  -lz \ # for ctelnet.cpp
  -lyajl \
  -lopengl32 \
  -lglut \
  -lglu32
  INCLUDEPATH += "C:\\mingw32\\include"
  # Leave this undefined so mudlet::readSettings() preprocessing will fall back 
to

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1676032] Re: Conform to CII best practices

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/811

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 #811
   https://github.com/Mudlet/Mudlet/issues/811

** 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/1676032

Title:
  Conform to CII best practices

Status in Mudlet:
  Opinion

Bug description:
  Something started by the Linux Foundation to help improve your
  projects CII - CII being defined as "A CII Best Practice is a process
  or method that, when executed effectively, leads to enhanced project
  performance. CII Best Practices have been proven through extensive
  industry use and/or validation.".

  I started with it at
  https://bestpractices.coreinfrastructure.org/projects/818, something
  to look into at a later point.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1670459] Re: Cmake on windows build broken

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/806

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 #806
   https://github.com/Mudlet/Mudlet/issues/806

** 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/1670459

Title:
  Cmake on windows build broken

Status in Mudlet:
  Opinion

Bug description:
  It seems to be currently broken in the release_30 branch and the
  closest I've got it to working is using the CMake GUI + MinGW
  makefiles:

  The C compiler identification is GNU 4.8.1
  The CXX compiler identification is GNU 4.8.1
  Check for working C compiler: C:/mingw32/bin/gcc.exe
  Check for working C compiler: C:/mingw32/bin/gcc.exe -- works
  Detecting C compiler ABI info
  Detecting C compiler ABI info - done
  Check for working CXX compiler: C:/mingw32/bin/g++.exe
  Check for working CXX compiler: C:/mingw32/bin/g++.exe -- works
  Detecting CXX compiler ABI info
  Detecting CXX compiler ABI info - done
  CMake Error at C:/Program Files 
(x86)/CMake/share/cmake-3.0/Modules/FindPackageHandleStandardArgs.cmake:136 
(message):
Could NOT find ZIP (missing: ZIP_INCLUDE_DIR)
  Call Stack (most recent call first):
C:/Program Files 
(x86)/CMake/share/cmake-3.0/Modules/FindPackageHandleStandardArgs.cmake:343 
(_FPHSA_FAILURE_MESSAGE)
cmake/FindZIP.cmake:77 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
src/CMakeLists.txt:363 (FIND_PACKAGE)

  
  Configuring incomplete, errors occurred!
  See also "C:/Users/Vadim.FURORENT/Desktop/New 
folder/CMakeFiles/CMakeOutput.log".

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1676542] Re: Certain characters have issues in GMCP composer

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/815

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 #815
   https://github.com/Mudlet/Mudlet/issues/815

** 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/1676542

Title:
  Certain characters have issues in GMCP composer

Status in Mudlet:
  Opinion

Bug description:
  There are several characters I've discovered have issues in the GMCP
  composer - \ has already been reported, it needs to be escaped as \\.
  This the composer does automatically if it opens a file with \ in it,
  outputting a \\ in the composer window, but when writing a new file,
  it must be manually escaped in the composer window.

  [ will send to the MUD just fine unescaped, but when you open a scroll
  with a [ in it, it disappears.

  a " will also send just fine without any escapes, but when opening
  scrolls you end up with a \ before every " in the composer window.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1672123] Re: deleteOldProfiles needs to handle modules

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/808

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 #808
   https://github.com/Mudlet/Mudlet/issues/808

** 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/1672123

Title:
  deleteOldProfiles needs to handle modules

Status in Mudlet:
  Opinion

Bug description:
  It currently only deletes old snapshots of profiles and maps, but not
  of modules. Users are reporting module folders of up to 16GB:
  http://forums.achaea.com/discussion/comment/355617/#Comment_355617.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1633797] Re: Copying text while the main window is scrolling quickly with a lot of text causes a crash

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/796

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 #796
   https://github.com/Mudlet/Mudlet/issues/796

** 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/1633797

Title:
  Copying text while the main window is scrolling quickly with a lot of
  text causes a crash

Status in Mudlet:
  Opinion

Bug description:
  Two users have said that if they try to copy something while a lot of
  text is incoming, Mudlet will crash.

  Haven't tested it myself yet, need to confirm.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1676124] Re: Mudlet 3.0 lags for a macOS user

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/812

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 #812
   https://github.com/Mudlet/Mudlet/issues/812

** 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/1676124

Title:
  Mudlet 3.0 lags for a macOS user

Status in Mudlet:
  Opinion

Bug description:
  The feedback on Discord is:

  3.0 is lagging on macOS :/

  when I'm walking on the path or around the town
  the info I get from location has delay

  I've the same latency in both clients
  but when I type direction e.g. I press keybind W (west) and it takes more 
time until I see new location description etc.

  
  times in debug from pressing keybind to see the 1st text
  3.0:
  693
  204
  301
  254
  271
  341
  275

  2.1:
  160
  158
  153
  154
  142
  154

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1676193] Re: Need a function to get the dimensions of an image

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/813

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 #813
   https://github.com/Mudlet/Mudlet/issues/813

** 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/1676193

Title:
  Need a function to get the dimensions of an image

Status in Mudlet:
  Opinion

Bug description:
  Need a function to get the dimensions of an image - since the labels
  require to be properly sized (or the mapper background). This is
  helpful for images you download, for example.

  Several people have been asking for this.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1674350] Re: Profiles won't install if special characters

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/810

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 #810
   https://github.com/Mudlet/Mudlet/issues/810

** 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/1674350

Title:
  Profiles won't install if special characters

Status in Mudlet:
  Opinion

Bug description:
  I was aware of this previously: When the package manager unzips, if
  there's a $ present in the system username the unzip/package install
  fails. It appears it's not just the presence of a $, it's many special
  characters.

  You group-say 'It's going to be the path /users/username/.config'
  You group-say 'if 'username' has something funky in it that might cause 
problems'
  You group-say 'Does your windows username have any special characters in it?'
  You group-say 'in particular a dollar sign?'
  Sobes group-says 'I think that Root profile is named in Russian'
  Sobes tells you 'yea, username is in win1251 codepage'

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1676759] Re: Investigate PCRE JIT for regex performance improvement

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/817

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 #817
   https://github.com/Mudlet/Mudlet/issues/817

** 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/1676759

Title:
  Investigate PCRE JIT for regex performance improvement

Status in Mudlet:
  Opinion

Bug description:
  http://sljit.sourceforge.net/pcre.html

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1652413] Re: DPI Awareness/Scaling Issues (Win10)

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/800

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 #800
   https://github.com/Mudlet/Mudlet/issues/800

** 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/1652413

Title:
  DPI Awareness/Scaling Issues (Win10)

Status in Mudlet:
  Opinion

Bug description:
  Summary:
  Mudlet exhibits behavior associated with static size values (in pixels) in 
the Qt GUI widgets rather than using relative values. Additionally, the 
application does not specify DPI awareness such that Qt autoscales the 
application using the native Windows display APIs.* As such, the UI is, while 
usable, not properly rendered which breaks third-party UI add-ons produced by 
the community.

  *More info here: http://doc.qt.io/qt-5/highdpi.html

  Recommended remediation (up for discussion!):
  While an effort to convert Mudlet's QML to relative values would be the 
"right" fix, the autoscaling provided by Qt 5.6+ and Windows 8.1+ allow for one 
of the following:

 The addition of a qt.conf directive to specify an equivalent of the 
following (passed at runtime, instructs Windows to treat the application as 
non-DPI aware and to scale it automatically):
-platform windows:dpiawareness=0

  OR

 The addition of the following property setter for Windows builds to 
achieve the same goal as option #1:
 QGuiApplication::setAttribute(Qt::AA_EnableHighDpiScaling);

  Steps to reproduce:
  Run the application on a High DPI Windows 10 machine such as a Microsoft 
Surface or 4K display with scaling enabled and set to a value other than 100%. 
Observe the UI scaling issues in the splash frame and Connections frame - 
particularly cut off text and oddly shaped fields/tiny small icons.

  I have tested the -platform windows:dpiawareness=0 solution and it's
  working with Mudlet3-iota built against Qt5.6 on Windows 10 following
  the wiki instructions. I am building and testing the second (probably
  preferable) fix.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1383998] Re: Code to keep track of area coordinate extremes incomplete

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/773

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 #773
   https://github.com/Mudlet/Mudlet/issues/773

** 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/1383998

Title:
  Code to keep track of area coordinate extremes incomplete

Status in Mudlet:
  Opinion

Bug description:
  Whilst fixing TArea::exits I spotted that the code that maintained the
  coordinate extremes in the x, y and z dimensions:
  "TArea::{min|max}_{x|y|z}" for the TArea classes and the x and y
  extremes for each used z axis value (there are also redundant values
  for the z axis): {x|y|z}{min|max}Ebene has been commented out and
  seems incomplete.  I suspect that work needs to be done in this area.

  One positive outcome for that is that it should be possible to improve
  both the 2 and 3D mapper widgets if they can be revised to use this
  data as it can be used to optimise the painting code (instead of
  checking each room in an area to see whether(2D map) or when (3D) it
  needs to be drawn based on checking its z-coordinate, having lists
  already to hand must make things faster)...

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1400508] Re: (Q)Event handling code not always using accept() or ignore() to signal attitude towards invoking events

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/774

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 #774
   https://github.com/Mudlet/Mudlet/issues/774

** 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/1400508

Title:
  (Q)Event handling code not always using accept() or ignore() to signal
  attitude towards invoking events

Status in Mudlet:
  Opinion

Bug description:
  The Qt documentation for QEvent (and subclasses) suggests that methods
  that handle such events should call accept() or ignore() on the
  (QEvent *) passed by the invoker {to set or reset the isAccepted flag}
  to indicate whether: EITHER the method "accepts" the event i.e. does
  "Handle" it and thus the event does NOT need to be passed further up
  the Widget chain in order for an ancestor to deal with it OR "ignores"
  it so that it disclaims responsibility for handling the event and does
  pass it on up to the parent.  It also notes that: "By default,
  isAccepted() is set to true, but don't rely on this as subclasses may
  choose to clear it in their constructor." unfortunately the
  documentation for individual sub classes do not seem to include this
  information, though I guess for some it can be inferred from the
  nature of their actions.

  A superficial search suggests the following may need these sort of things:
  void T2DMap::mouseDoubleClickEvent ( QMouseEvent * )
  void T2DMap::mouseReleaseEvent( QMouseEvent * )
  bool T2DMap::event( QEvent * )
  void T2DMap::mousePressEvent( QMouseEvent * )
  void T2DMap::mouseMoveEvent( QMouseEvent * )
  bool TCommandLine::event( QEvent * ) <- some code branches already have 
accept() others may need to have ignored() added.
  void TCommandLine::focusInEvent( QFocusEvent * )
  void TCommandLine::focusOutEvent( QFocusEvent * )
  void TCommandLine::mousePressEvent( QMouseEvent * ) <- I suspect that if 
ignore() was used it would not need to raise a QPlainTextEdit::mousePressEvent( 
QMouseEvent * ) as the last line to deal with unhandled events.
  void TConsole::resizeEvent( QResizeEvent * ) <- I suspect this automatically 
clears the accept flag so the event gets propagated upwards, else the 
QWidget::resizeEvent( QResizeEvent * ) it includes produces a similar effect.
  void TConsole::showEvent( QShowEvent * )
  void TConsole::hideEvent( QShowEvent * )
  void TLabel::mousePressEvent( QMouseEvent * )
  void TLabel::leaveEvent( QEvent * )
  void TLabel::enterEvent( QEvent * ) <- all three are like 
TCommandLine::mousePressEvent()

  ... etc, etc.  Blimey, there are more to check than I at first
  thought!

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1420537] Re: 256 color does not work in Materia Magica

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/779

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 #779
   https://github.com/Mudlet/Mudlet/issues/779

** 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/1420537

Title:
  256 color does not work in Materia Magica

Status in Mudlet:
  Opinion

Bug description:
  256 color does not work in Materia Magica. It does work properly in
  Aardwolf so Im not sure if the issue is with Materia Magica or Mudlet.
  256 color does work when I use MUSHclient in Materia Magica if that
  matters. I have tried in 2.1 and 3.0delta and still does not work. I
  use win 8.1 and have also tried on my other pc which runs win 7.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1471406] Re: Insuffienctly well defined object types could theoretically at least cause problems

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/784

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 #784
   https://github.com/Mudlet/Mudlet/issues/784

** 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/1471406

Title:
  Insuffienctly well defined object types could theoretically at least
  cause problems

Status in Mudlet:
  Opinion

Bug description:
  In a forum post inquiring about the maximum number of room IDs that
  could be used {http://forums.mudlet.org/viewtopic.php?f=13=4825} I
  realised that the TRoom::roomId member is specified as an "int" but as
  far as I understand it as a signed integer (using 16 bits in total) is
  only guaranteed to have a maximum positive value of 2^16-1 or 32767 -
  now in practice it is likely to be using 4 bytes but it need not be
  so.

  I would suggest that for this variable - and indeed *for* *all* *simple* 
*numeric* *types* *that* *get* *stored* *in* *a* *file* we define precisely the 
size of the object using the Qt provided signed/unsigned types:
  quint16, qint16
  quint32, qint32
  quint64, qint64

  For the map file I suggest the next time we revise the format we
  change to read/write the above types, and downgrade to reading generic
  "ints" etc. from old file formats.

  For the Mudlet profile I note that we write a version 1.0 into the
  start BUT WE HAVE COMMENTED OUT THE CHECK FOR THIS ON READING IN
  EXISTING CODE - that needs to be reimplemented ASAP to minimise
  "current" code getting broken when we do fix a few items in the future
  (e.g. the command "seperater"/"separator" element cock-up) as the
  existing code in the field will break or at least spew out "not
  understood element" debug messages on future "new/improved/fixed"
  saved files.

  Also, in regard to char types (Qt offers: quint8 & qint8): whilst the
  char type is definitely 8 bits I note especially in the cTelnet class
  some cases where it is not entire clear whether it is used as a signed
  or unsigned object - as used it suggests signed but when e.g. we use
  constants for Telnet options that are more than 127 in value - this
  implies unsigned values may be put into plain "char" variables.

  The Qt documents themselves also note:
  "
  QDataStream's binary format has evolved since Qt 1.0, and is likely to 
continue evolving to reflect changes done in Qt. When inputting or outputting 
complex types, it's very important to make sure that the same version of the 
stream (version()) is used for reading and writing. If you need both forward 
and backward compatibility, you can hardcode the version number in the 
application:

  stream.setVersion(QDataStream::Qt_4_0);
  "

  We do not currently do this, so, theoretically if someone tries to
  load a map file format version 4 (the earliest that we still support)
  there is no guarantee that the current Qt libraries will parse the
  serialized bytes in the same manner as they did in the past - however
  by addressing that, this become an issue that we can solve for the
  future.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1479525] Re: Profile "Notes" reader does not close file after reading

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/788

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 #788
   https://github.com/Mudlet/Mudlet/issues/788

** 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/1479525

Title:
  Profile "Notes" reader does not close file after reading

Status in Mudlet:
  Opinion

Bug description:
  Just looking through the current-ish code-base for something and
  spotted that (void)dlgNotepad::restore() does not close the QFile that
  it opens to read the notes.txt file in the root of the profile's
  directory tree - and both it and the corresponding save method,
  (void)dlgNotepad::save() have absolutely no error handling...

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1409526] Re: getColorWildcard() returns too much of a match

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/776

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 #776
   https://github.com/Mudlet/Mudlet/issues/776

** 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/1409526

Title:
  getColorWildcard() returns too much of a match

Status in Mudlet:
  Opinion

Bug description:
  See http://forums.mudlet.org/viewtopic.php?f=5=4684=22294#p22292.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1458723] Re: Mudlet cannot send POST requests

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/782

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 #782
   https://github.com/Mudlet/Mudlet/issues/782

** 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/1458723

Title:
  Mudlet cannot send POST requests

Status in Mudlet:
  Opinion

Bug description:
  Copied by request of SlySven from
  http://forums.mudlet.org/viewtopic.php?f=7=4795

  I found myself looking at the pastebin API earlier and realized
  currently Mudlet doesn't seem to support sending POST requests to
  servers. From what I'm seeing from the first result of a cursory
  search (https://stackoverflow.com/questions/12487620/correct-format-
  for-http-post-using-qnetworkrequest#12487795), this could be
  incorporated easily by adding an optional argument to downloadFile.
  The pastebin API in particular specifically requires UTF-8 encoding as
  well, which I'm not entirely sure if is an issue currently or not.
  Assuming there isn't a reason this is particularly difficult or
  undesirable, it should be a quick modification in the same code block
  as the user-agent fix
  (https://bugs.launchpad.net/mudlet/+bug/1366781).

  I'm not honestly sure how many other purposes this would actually
  benefit, but I assume there are other relevant APIs requiring POST
  rather than GET as well.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1412111] Re: New trigger icon for a trigger in a disabled group is colourised

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/777

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 #777
   https://github.com/Mudlet/Mudlet/issues/777

** 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/1412111

Title:
  New trigger icon for a trigger in a disabled group is colourised

Status in Mudlet:
  Opinion

Bug description:
  The new trigger icon for a trigger in a disabled group is colourised,
  while it should be monochrome.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1421505] Re: Main window font 1 pt higher than it should be

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/781

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 #781
   https://github.com/Mudlet/Mudlet/issues/781

** 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/1421505

Title:
  Main window font 1 pt higher than it should be

Status in Mudlet:
  Opinion

Bug description:
  I'm sorry if this is trivial but the font size listed in settings >
  main display shows a value of one point font size higher than it's
  actual size. The mini console font size however is correct. For
  example the main window font set at 11 would match a mini console font
  of 10.  This happens in 2.1 and 3.0d mudlet versions. I use win 8.1
  and win 7.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1421502] Re: Reset all colors to default "Foreground" bug

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/780

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 #780
   https://github.com/Mudlet/Mudlet/issues/780

** 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/1421502

Title:
  Reset all colors to default "Foreground" bug

Status in Mudlet:
  Opinion

Bug description:
  In a fresh profile go to settings > profile preferences under the
  color view tab, the default for the foreground color is  Hue: 0 Sat: 0
  Val: 192 Red: 192 Green: 192 Blue: 192. When I click the reset all
  colors to default button the foreground changes to Hue: 0 Sat: 0 Val:
  255 Red: 255 Green: 255 Blue: 255.  I noticed this when playing with
  colors and my foreground was bright white after resetting. This is in
  mudlet 2.1 and 3.0d. I use win 8.1 and win 7.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1468743] Re: Feature Request: Hideable rooms

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/783

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 #783
   https://github.com/Mudlet/Mudlet/issues/783

** 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/1468743

Title:
  Feature Request: Hideable rooms

Status in Mudlet:
  Opinion

Bug description:
  The current Mudlet codebase (2.1 release, 3.0.0 previews) do not have
  the ability to "hide" rooms like, say, the TinTin++ MUD Client.  A
  user had inquired about this facility.
  http://forums.mudlet.org/viewtopic.php?f=13=4821

  Whilst it would not be too hard to provide a boolean flag for a room in the 
TRoom class (or possibly from an implementation detail, there might be merit in 
doing so in the containing TArea - I have visions in the future of permitting a 
room to be in multiple Areas {it's coordinates then become an TArea property 
rather than a TRoom one}) - there might need to be a discussion about:
  * whether a "hidden" room still has exits draw towards it, or if those need 
to be individually hidden as well
  * under what situation the hide might need to be overridden and whether other 
aspects of the room need to be concealed
  * as an open source project there is nothing to prevent code changes to 
"reveal" any hidden data that a MUD might wish to include in a pre-distributed 
map.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1501526] Re: No removeCustomLine() Lua command

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/791

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 #791
   https://github.com/Mudlet/Mudlet/issues/791

** 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/1501526

Title:
  No removeCustomLine() Lua command

Status in Mudlet:
  Opinion

Bug description:
  Whilst added missing documentation for addCustomLine() and
  getCustomLines() to the wiki I found that there is no corresponding
  command to remove a specified custom exit line for a given exit from a
  given room...

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1516558] Re: Mudlet issues a "faux" send when connecting to any Rhost-based MU* games.

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/792

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 #792
   https://github.com/Mudlet/Mudlet/issues/792

** 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/1516558

Title:
  Mudlet issues a "faux" send when connecting to any Rhost-based MU*
  games.

Status in Mudlet:
  Opinion

Bug description:
  As noted here:

  http://forums.mudlet.org/viewtopic.php?f=9=4911

  When connecting to a Rhost-based game (one can test at:
  iweb.localecho.net:4201), one will have to enter any log-in commands,
  such as connect or create, twice in order for them to go through. The
  first attempt doesn't seem to generate any actual output to the MU*
  other than as a carriage return (the main menu pops up again as though
  one had pressed enter.)

  Mudlet: 2.1
  OS: Windows 8.1

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1582110] Re: Mudlet mishandles MCCP in CoffeeMUD

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/794

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 #794
   https://github.com/Mudlet/Mudlet/issues/794

** 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/1582110

Title:
  Mudlet mishandles MCCP in CoffeeMUD

Status in Mudlet:
  Opinion

Bug description:
  I'm running self-compiled variant of 3.0.0, Git revision 4f6a41d.

  I'm playing CoffeeMUD coffeemud.net port 2323.
  When MCCP is turned on in settings, Mudlet doesn't display some lines of the 
output.
  I know Mudlet receives these lines because I see them in the "recordings" 
Mudlet makes.
  I know the server works correctly because MUSHclient displays the same data 
just fine.

  I'm attaching 2 screenshots where you can observe that the lines 'You
  gain 73 experience points' and 'You get 9 gold ...' are not displayed.
  This might, or might not be connected to the SOUND tag preceding them.

  This bug disappears when I force compression off.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1380455] Re: MXP line tag 4 does not revert to prior mode at end of tag

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/772

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 #772
   https://github.com/Mudlet/Mudlet/issues/772

** 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/1380455

Title:
  MXP line tag 4 does not revert to prior mode at end of tag

Status in Mudlet:
  Opinion

Bug description:
  The MXP spec says that line tag 4 should enable secure mode, but only
  for the next tag. It should revert back to its prior mode after the
  tag has closed. When Mudlet receive line tag 4, it switches to secure
  mode, but it sticks permanently rather than reverting back as it
  should. This causes some problems for certain MUDs. For example, in
  Lusternia (and presumably other IRE MUDs), they exclusively send MXP
  via line tag 4 for their MXP command. When a user turns off MXP on the
  server, Lusternia stops sending MXP commands to Mudlet. But, Mudlet is
  still stuck in MXP security mode because it didn't revert back at the
  end of each tag. This causes it to squelch anything between a < and >,
  mistakingly thinking them as MXP tags.

  MXP references:
  
https://web.archive.org/web/20101023084054/http://www.mudstandards.org/MXP_Line_Tags
  www.zuggsoft.com/zmud/mxp.htm#MXP%20Line%20Tags

  I have attached a patch to fix this bug.

  If you want to reproduce the bug, here are steps using Lusternia as your host 
(or possibly any IRE game). Enter these commands:
  CONFIG MXP ON
  CONFIG MXP OFF
  SAY 

  With this bug, the second  that is echoed back is squelched. With
  my patch, it works fine.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1369190] Re: Move mudlet-lua repository into Mudlet organisation

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/765

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 #765
   https://github.com/Mudlet/Mudlet/issues/765

** 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/1369190

Title:
  Move mudlet-lua repository into Mudlet organisation

Status in Mudlet:
  Opinion

Bug description:
  https://github.com/vadi2/mudlet-lua should be moved under
  https://github.com/Mudlet.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1378136] Re: Broken program logic in dlgConnectionProfiles dialog: assumes profile directory exists when this is not guaranteed for "predefined" MUD ones

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/770

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 #770
   https://github.com/Mudlet/Mudlet/issues/770

** 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/1378136

Title:
  Broken program logic in dlgConnectionProfiles dialog: assumes profile
  directory exists when this is not guaranteed for "predefined" MUD ones

Status in Mudlet:
  Opinion

Bug description:
  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 the dialog is opened.  It transpires that each time a new icon is
  selected the data for the old one is written out to various files that
  would be in the profile directory for that profile e.g. "url", "port",
  "description".  However the Predefined MUDs, if they have never
  actually been used, will not have had a profile directory created for
  them (I suspect but have not confirmed that the directory is created
  at the point when the "Connect" action is initiated) - as a
  consequence Mudlet will try to create the aforesaid files "url" et al.
  in a non-existent directory, this will fail and cause the error
  message seen.

  Note that it would not seem to me to be acceptable to create the
  profile directories that each of the "Predefined" MUD servers would
  need as this would add 15 or so more sub-trees under the
  ~/.config/mudlet/profiles directory.

  The attached diff modifies dlgConnectionProfiles::writeProfileData(
  QString profile, QString item, QString what ) to show the problem but
  I do not know whether by muting the warning output this would be
  enough to solve the issue.  It may be that the logic behind the class
  needs some review...

  I'd suggest this be rated as Medium importance at the minimum.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1256553] Re: Long command lines are not affected by client word wrapping

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/753

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 #753
   https://github.com/Mudlet/Mudlet/issues/753

** 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/1256553

Title:
  Long command lines are not affected by client word wrapping

Status in Mudlet:
  Opinion

Bug description:
  Entering say, a paragraph of text into the MUD wraps the echoed
  command text by default at 100 characters regardless of word wrap
  setting.

  Mudlet 2.1, WinXP Pro

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1327914] Re: Background label limits mapper functionality

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/764

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 #764
   https://github.com/Mudlet/Mudlet/issues/764

** Changed in: mudlet
   Status: Confirmed => Opinion

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

Title:
  Background label limits mapper functionality

Status in Mudlet:
  Opinion

Bug description:
  Mudlet 2.1
  Win XP

  If the mapper widget is drawn over an underlying label, wherever the
  two overlap the dragging functionality for moving rooms will not work.
  (http://forums.mudlet.org/viewtopic.php?f=13=4534)

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1369436] Re: Jarring effect on refresh

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/766

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 #766
   https://github.com/Mudlet/Mudlet/issues/766

** 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/1369436

Title:
  Jarring effect on refresh

Status in Mudlet:
  Opinion

Bug description:
  There's a jarring effect that happens when you click again on a large
  item, especially from the search window. Pretty undesirable to have.
  Attached is a screencast and an alias to demonstrate the issue.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1282885] Re: copy() function truncates selection in latest git

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/760

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 #760
   https://github.com/Mudlet/Mudlet/issues/760

** 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/1282885

Title:
  copy() function truncates selection in latest git

Status in Mudlet:
  Opinion

Bug description:
  This is on a version of mudlet compiled on 64-bit Arch Linux from a git 
snapshot 02-20-2014. 
  When trying to copy lines from the main buffer to a MiniConsole using 
selectCurrentLine()
copy()
appendBuffer("windowname")
  lines more than 81 characters long get truncated in the MiniConsole. The 
truncation happens at word boundaries, as though for line wrapping. The 
MiniConsole is set to wrap at 55 characters, and does. The main window wraps at 
95 characters, also without issue.
  Using selectString(line,1) instead of selectCurrentLine() shows the same 
effect. Coloring the line, using fg(), colors the full line, indicating that 
the issue is not with the selection being truncated. Both appendBuffer() and 
paste() show truncated output, which suggest that it's copy() doing the 
truncating; it's also possible that it's a problem affecting both of those 
functions. I'm unaware of a way to query the contents of the clipboard from 
within mudlet to check more directly.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1379503] Re: getModulePriority() errors if a module doesn't exist

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/771

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 #771
   https://github.com/Mudlet/Mudlet/issues/771

** 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/1379503

Title:
  getModulePriority() errors if a module doesn't exist

Status in Mudlet:
  Opinion

Bug description:
  getModulePriority() errors if a module doesn't exist - it should be
  returning nil + error message instead.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1322773] Re: Vertical gauges show as full when at 0 value

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/763

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 #763
   https://github.com/Mudlet/Mudlet/issues/763

** 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/1322773

Title:
  Vertical gauges show as full when at 0 value

Status in Mudlet:
  Opinion

Bug description:
  Mudlet 2.1
  Win XP (but also tested on linux)

  When set to 0 value, vertical gauges show as if they are at 100
  (values 1-100 are fine). See whole thread here:
  http://forums.mudlet.org/viewtopic.php?f=9=4506

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1371849] Re: copy() & appendBuffer() not keeping links

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/768

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 #768
   https://github.com/Mudlet/Mudlet/issues/768

** 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/1371849

Title:
  copy() & appendBuffer() not keeping links

Status in Mudlet:
  Opinion

Bug description:
  copy() & appendBuffer() might not keeping links; they didn't a while
  ago anyway. Need to verify that is not the case anymore.

  Also see
  http://forums.mudlet.org/viewtopic.php?f=9=2237=9642#p9642.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1261095] Re: Improve getLines() to be useable on a miniconsole

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/754

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 #754
   https://github.com/Mudlet/Mudlet/issues/754

** 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/1261095

Title:
  Improve getLines() to be useable on a miniconsole

Status in Mudlet:
  Opinion

Bug description:
  Improve getLines() to be useable on a miniconsole - right now, you can
  only use it on the main window.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1263240] Re: Trigger regex compile message does not explain the error

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/755

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 #755
   https://github.com/Mudlet/Mudlet/issues/755

** 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/1263240

Title:
  Trigger regex compile message does not explain the error

Status in Mudlet:
  Opinion

Bug description:
  It's nice that it says there is a problem, but it does not actually
  describe the problem. It should be possible to do so, see screenshot
  of another tool doing this.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1266260] Re: Code omission: room removal does not remove (TArea *)->exits that exit TO that room

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/757

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 #757
   https://github.com/Mudlet/Mudlet/issues/757

** 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/1266260

Title:
  Code omission: room removal does not remove (TArea *)->exits that exit
  TO that room

Status in Mudlet:
  Opinion

Bug description:
  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 be recorded as the first pair member of the inner part
  of a TArea's exits member {a QMap structured as:  >}
  then that entry is removed. Unfortunately this would seem to require a
  scan through every but the deleted room's TAreas' exits...

  In current code, of course, the exits member is not used however I
  understand discussions over map route finding may touch on inter-area
  links of which this is a resource that would be directly relevant.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1371267] Re: Mudlet doesn't report profile save or export error when there is no more disk space

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/767

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 #767
   https://github.com/Mudlet/Mudlet/issues/767

** 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/1371267

Title:
  Mudlet doesn't report profile save or export error when there is no
  more disk space

Status in Mudlet:
  Opinion

Bug description:
  Mudlet doesn't report profile save or export error when there is no
  more disk space to save in the location it is saving in.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1318256] Re: Serialization/deserialization issues

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/762

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 #762
   https://github.com/Mudlet/Mudlet/issues/762

** 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/1318256

Title:
  Serialization/deserialization issues

Status in Mudlet:
  Opinion

Bug description:
  People are losing their stuff, it's a real thing, need to work out why
  and fix it.

  Some examples:
  http://forums.mudlet.org/viewtopic.php?f=9=4505=20878#p20878

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1218614] Re: Temporary timers & triggers Lua code be marked for deletion after they've executed

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/737

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 #737
   https://github.com/Mudlet/Mudlet/issues/737

** 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/1218614

Title:
  Temporary timers & triggers Lua code be marked for deletion after
  they've executed

Status in Mudlet:
  Opinion

Bug description:
  Temporary timers & triggers Lua code should be marked for deletion
  after they've executed. Lua's incremental GC will account for actually
  deleting them in bits as it's necessary, so it will not be a
  performance hit (just like it hasn't been already for many user
  scripts).

  The current setup creates a memory leak.

  See http://forums.mudlet.org/viewtopic.php?f=7=3593 for the original
  report.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1254208] Re: Mac Mudlet needs to be signed

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/751

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 #751
   https://github.com/Mudlet/Mudlet/issues/751

** 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/1254208

Title:
  Mac Mudlet needs to be signed

Status in Mudlet:
  Opinion

Bug description:
  Mac Mudlet needs to be signed, otherwise it complains of 'Unknown
  Developer' and doesn't run when it is double-clicked either - you have
  to right-click and open. Generally, an inconvenience Apple has
  introduced to get people to sign their apps.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1234540] Re: Raise an event when all scripts have finished loading

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/746

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 #746
   https://github.com/Mudlet/Mudlet/issues/746

** 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/1234540

Title:
  Raise an event when all scripts have finished loading

Status in Mudlet:
  Opinion

Bug description:
  Mudlet should raise an event when all scipts have finished loading.
  This'll allow scripts that need functions from other scripts already
  declared to load easier.

  At the moment, the original script itself can raise an event
  mentioning that it is ready - but not all packages do this, as it is
  not automatic.

  Alternatively, one can use a tempTimer with a time of 0 to get their
  code to run after other scripts have loaded - but that is ugly.

  Raising an event when all scripts are loaded would be similar to
  Javascript, where document.ready can be used to run your stuff once
  all scripts and page content has loaded.

  This was based off this conversation:
  (15:57:04) Ephemeral: hi, i'm having a problem where i've extended on some 
other people's scripts in a seperate package and for some reason if i don't 
deactivate and reactivate the script after starting the client up, none of the 
commands work and error out instead
  (15:57:28) Ephemeral: is there like an event akin to document.ready in 
javascript where I can trigger a script to load after all other scripts have?
  (16:24:19) vadi: Hello!
  (16:25:30) vadi: Ephemeral: Yes, the issue you're having is indeed because 
other scripts have not loaded when you're trying to run yours - and you 'fix' 
it by re-running after others have loaded
  (16:26:00) vadi: There isn't a specific event in Mudlet per-se (though that'd 
be a good idea, haven't thought about it that way) - typically whatever you're 
dependant on ought to raise an event when it has loaded, then you can hook your 
script on it. 
  (16:26:25) vadi: If it doesn't do that, there is a trick you can do - in your 
script, use tempTimer(0, function()  end) - it will run after 
all scripts have loaded.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1247274] Re: 'About > download latest version' is misleading for some platforms

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/749

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 #749
   https://github.com/Mudlet/Mudlet/issues/749

** 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/1247274

Title:
  'About > download latest version' is misleading for some platforms

Status in Mudlet:
  Opinion

Bug description:
  The latest Mudlet downloads for OSX, Linux-based OSs are at
  http://www.mudlet.org/download while the link takes the users to
  http://sourceforge.net/projects/mudlet/files/ which is only latest for
  Windows.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1218615] Re: errors.txt is still created even though we never use it and it's depricated

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/738

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 #738
   https://github.com/Mudlet/Mudlet/issues/738

** 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/1218615

Title:
  errors.txt is still created even though we never use it and it's
  depricated

Status in Mudlet:
  Opinion

Bug description:
  We use the errors view instead now - errors.txt shouldn't be created
  anymore.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1239835] Re: Sync with latest lua-yajl

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/747

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 #747
   https://github.com/Mudlet/Mudlet/issues/747

** 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/1239835

Title:
  Sync with latest lua-yajl

Status in Mudlet:
  Opinion

Bug description:
  They had an update 9 months ago that fixes a bug:
  https://github.com/brimworks/lua-yajl

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1232325] Re: Creating a trigger with permSubstringTrigger and then putting a trigger into it doesn't turn the group in Mudlet into a folder

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/745

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 #745
   https://github.com/Mudlet/Mudlet/issues/745

** 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/1232325

Title:
  Creating a trigger with permSubstringTrigger and then putting a
  trigger into it doesn't turn the group in Mudlet into a folder

Status in Mudlet:
  Opinion

Bug description:
  When you create a trigger group with:

  permSubstringTrigger("Combat triggers", "", {""}, "")

  And then put a trigger inside it with:

  permSubstringTrigger("Highlight stuff", "Combat triggers", {"pixie"},
  [[selectString(line, 1) bg("yellow") resetFormat()]])

  The parent group does not become a folder, and gives error saying it
  is missing a pattern. In this case, it should auto-convert to a group
  instead.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1245499] Re: send NAWS when changing wrap-around column

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/748

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 #748
   https://github.com/Mudlet/Mudlet/issues/748

** 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/1245499

Title:
  send NAWS when changing wrap-around column

Status in Mudlet:
  Opinion

Bug description:
  When editing in

  settings -> main window

  the "wrap around at" column

  the server isn't notified with a telnet NAWS sub negotiation that the
  terminal width has changed

  (it indeed has changed, since sending a NAWS request manually will
  yield the new value)

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1249741] Re: missing lua-zip and lua-filesystem dependencies (Debian/Ubuntu)

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/750

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 #750
   https://github.com/Mudlet/Mudlet/issues/750

** Changed in: mudlet
   Status: Confirmed => Opinion

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

Title:
  missing lua-zip and lua-filesystem dependencies (Debian/Ubuntu)

Status in Mudlet:
  Opinion

Bug description:
  Dependencies on lua-zip and lua-filesystem are missing. Arguably lua-
  zip would only be a recommendation as it's only required for package
  importing, but that seems silly

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1228163] Re: cinsertText() makes simple "highlight triggers" not align

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/743

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 #743
   https://github.com/Mudlet/Mudlet/issues/743

** 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/1228163

Title:
  cinsertText() makes simple "highlight triggers" not align

Status in Mudlet:
  Opinion

Bug description:
  Mudlet 2.1 for windows in Window 7 professional 64bit

  when using cinsertText() (and probably insertText() too) all simple 
highlights (simple meaning triggers with the option "highlight" ticked and not 
by selectString highlighting) get displaced/moved back by the string length of 
what is inserted.
  In the attachment you can see a rune description being inserted "(raido: 
return location)", "Babel" being highlighted by selectString and the rest of 
the highlights being off place. What was supposed to be highlighted: "gold" 
instead of "hip", "Ashtan" instead of "a smi", "east" instead of "mana" and 
"monolith" instead of "of a sm".

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1226485] Re: Allow fallback paths for modules

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/742

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 #742
   https://github.com/Mudlet/Mudlet/issues/742

** 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/1226485

Title:
  Allow fallback paths for modules

Status in Mudlet:
  Opinion

Bug description:
  One usercase I was presented today - a user is syncing their profiles
  via Dropbox across different OSes, but modules don't work (because of
  obviously different paths, even within the Dropbox context).

  So an idea is to allow fallback paths for modules - if one doesn't
  work, another will be tried.

  UI-wise, something that would allow you to click on a [+] button in
  the path field and adds an extra row for the new path(s) would work.
  There shouldn't be a limit on the paths, so as to support multiple
  computers with different layout configurations.

  A current workaround is to simply install the modules several times,
  so it fails the and loads the one it can.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1225256] Re: Unnecessary folder in packages

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/740

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 #740
   https://github.com/Mudlet/Mudlet/issues/740

** 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/1225256

Title:
  Unnecessary folder in packages

Status in Mudlet:
  Opinion

Bug description:
  See attached sample package - it attached a folder with the sample
  structure of my home folder (revelating my username) which was empty.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1226355] Re: Pre-uninstall event

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/741

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 #741
   https://github.com/Mudlet/Mudlet/issues/741

** 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/1226355

Title:
  Pre-uninstall event

Status in Mudlet:
  Opinion

Bug description:
  It would be good to get an event raised before a package is
  uninstalled - so the package can delete its temporary objects and
  clean up properly.

  This would remove the current annoying need to restart Mudlet upon a
  package reinstall/upgrade, which has to be done because of all of the
  temporary objects getting duplicated.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1229978] Re: setLabelStyleSheet() needs improvement in error handling

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/744

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 #744
   https://github.com/Mudlet/Mudlet/issues/744

** 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/1229978

Title:
  setLabelStyleSheet() needs improvement in error handling

Status in Mudlet:
  Opinion

Bug description:
  setLabelStyleSheet() currently only checks the two arguments to it
  needed, and fails to notify when the label it is operating on is
  missing
  (http://sourceforge.net/p/mudlet/code/ci/master/tree/src/TConsole.cpp#l590).
  It also doesn't notify then the CSS is invalid, but Qt doesn't seem to
  support us there in that regard.

  If the label setLabelStyleSheet() tries to operate on is missing, the
  function should return nil, "setLabelStyleSheet: label $labelname"
  doesn't exist"

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1217165] Re: Hide default_host from the list of profiles

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/736

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 #736
   https://github.com/Mudlet/Mudlet/issues/736

** 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/1217165

Title:
  Hide default_host from the list of profiles

Status in Mudlet:
  Opinion

Bug description:
  At least one user was using it accidentally and crashing Mudlet
  (bad!): http://forums.mudlet.org/viewtopic.php?f=9=3579

  I'm not sure on the need of it - if it's not needed anymore or could
  be restructured so we don't need it, maybe that is a better solution?

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1189668] Re: closeUserWindow() doesn't close a userwindow

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/721

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 #721
   https://github.com/Mudlet/Mudlet/issues/721

** 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/1189668

Title:
  closeUserWindow() doesn't close a userwindow

Status in Mudlet:
  Opinion

Bug description:
  closeUserWindow() doesn't close a userwindow. Try:

  openUserWindow("test")
  closeUserWindow("test")

  This leaves a window open.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1192396] Re: Loading a map on a new profile causes 'you have no map' dialog

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/724

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 #724
   https://github.com/Mudlet/Mudlet/issues/724

** 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/1192396

Title:
  Loading a map on a new profile causes 'you have no map' dialog

Status in Mudlet:
  Opinion

Bug description:
  Steps to reproduce:

  * create new profile
  * do not open mapper, but go to settings and load a map in
  * mapper auto-opens
  * check for map happens, sees no map, shows dialog "do you want to download a 
map or start your own?"
  * this makes no sense because I *am* loading a map in

  I think the dialog should definitely stay there because it has been
  useful, but it needs to be able to handle this special case.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1190943] Re: Spellchecker highlighter is not showing on Ubuntu

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/723

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 #723
   https://github.com/Mudlet/Mudlet/issues/723

** 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/1190943

Title:
  Spellchecker highlighter is not showing on Ubuntu

Status in Mudlet:
  Opinion

Bug description:
  Spellchecker highlighter is not showing on Ubuntu (12.04) - I'm not
  sure since when, but it's been so for a while now. I can still right-
  click on words that are spelt wrong to get replacement suggestions,
  but the word itself is not underlined in red.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1203405] Re: Investigate the feasibility of a mobile view for forums

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/729

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 #729
   https://github.com/Mudlet/Mudlet/issues/729

** 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/1203405

Title:
  Investigate the feasibility of a mobile view for forums

Status in Mudlet:
  Opinion

Bug description:
  Reading and writing on the forums via a phone is very difficult right
  now - it'd be good to install something that would make this process
  be easier. Need to find out if there's any good options out there for
  enabling this.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1189660] Re: Mudlet saves scripts on script window open, not on close

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/720

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 #720
   https://github.com/Mudlet/Mudlet/issues/720

** 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/1189660

Title:
  Mudlet saves scripts on script window open, not on close

Status in Mudlet:
  Opinion

Bug description:
  While helping a new user, it was brought to my attention that when you
  open the scripts window, it saves whatever script was last selected.
  To test, you can make 2 simple scripts in an empty profile.

  Script one, named "Fizz", just does send("Fizz")
  Script two, named "Buzz", just does send("Buzz")

  If you then click on Fizz, close the script window, and reopen it, it
  will send "Fizz". Click on Buzz and it will send "Fizz" again, as
  expected (because it saved the Fizz script, which executes it). If you
  close the script window while Buzz is selected, it does not send
  "Buzz" but does send it when you reopen the script window.

  Saving the script object when the window opens is unexpected
  behaviour. It would make sense to either save it when you close the
  window, or to not save it at all (provide a way out without saving).
  But saving when you open the window could easily lead to unintended
  consequences, especially if the user is unaware that this happens.
  I'm an advanced Mudlet user who's been using it since the very
  beginning and just found out about the behaviour, so it seems likely
  most others are unaware of this as well.

  Tested using Mudlet-2.1 and Ubuntu 11.04 32bit with PAE.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1203404] Re: Upgrade PHP

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/728

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 #728
   https://github.com/Mudlet/Mudlet/issues/728

** 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/1203404

Title:
  Upgrade PHP

Status in Mudlet:
  Opinion

Bug description:
  As per https://www.phpbb.com/community/viewtopic.php?f=14=2152375,
  newer phpBB releases will require a new PHP version on the server.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1210714] Re: Notes window sometimes prints in non-monospace font

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/733

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 #733
   https://github.com/Mudlet/Mudlet/issues/733

** 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/1210714

Title:
  Notes window sometimes prints in non-monospace font

Status in Mudlet:
  Opinion

Bug description:
  Opening up the notes window and typing some more text in, the new text
  was not monospaced (see screenshot).

  It wasn't monospaces after closing and re-opening the window either.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1205515] Re: Upgrade make.mudlet.org's Wordpress install

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/730

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 #730
   https://github.com/Mudlet/Mudlet/issues/730

** 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/1205515

Title:
  Upgrade make.mudlet.org's Wordpress install

Status in Mudlet:
  Opinion

Bug description:
  Please upgrade make.mudlet.org's Wordpress install. It has some
  permission issues as well which'll hinder that.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1184770] Re: Multiline/AND highlighting highlights with only first line matched

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/718

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 #718
   https://github.com/Mudlet/Mudlet/issues/718

** 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/1184770

Title:
  Multiline/AND highlighting highlights with only first line matched

Status in Mudlet:
  Opinion

Bug description:
  When defining a multiline/AND trigger and checking the highlight box
  to make it a colorizer trigger, if the first pattern matches, it will
  be highlighted, regardless of whether subsequent triggers match. For
  example, the following trigger:

  1) It is very dark.  Exact match type
  2) return false  Lua code type
 multiline/AND, line delta 0

  will highlight the line "It is very dark."

  I suspect that the highlight box is not really intended to be used
  with multiline triggers, but it should either be fixed so that it only
  highlights if the whole trigger matches, or just disabled entirely for
  multiline triggers.

  This is on a version built from a 3/10/2013 git checkout, on running
  in Linux

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1195478] Re: Searches What field should trim data

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/725

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 #725
   https://github.com/Mudlet/Mudlet/issues/725

** 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/1195478

Title:
  Searches What field should trim data

Status in Mudlet:
  Opinion

Bug description:
  The searches 'what' field should trim its data (remove prefixed and
  trailing spaces), because indentation of some scripts really pushes
  the results out for no reason. See attached screenshot.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1200879] Re: lockRoom status is not reflected in roomLocked() until centerview()

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/726

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 #726
   https://github.com/Mudlet/Mudlet/issues/726

** 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/1200879

Title:
  lockRoom status is not reflected in roomLocked() until centerview()

Status in Mudlet:
  Opinion

Bug description:
  When you change the status of a room with lockRoom() and check it
  right after with roomLocked(), the change is not reflected until you
  use centerview().

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1184754] Re: IRC linkifier doesn't get the last letter of a url

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/717

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 #717
   https://github.com/Mudlet/Mudlet/issues/717

** 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/1184754

Title:
  IRC linkifier doesn't get the last letter of a url

Status in Mudlet:
  Opinion

Bug description:
  The linkifier in the IRC fails to to linkify the whole url, forgetting
  the last character.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1189714] Re: é cannot be typed on Mac

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/722

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 #722
   https://github.com/Mudlet/Mudlet/issues/722

** 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/1189714

Title:
  é cannot be typed on Mac

Status in Mudlet:
  Opinion

Bug description:
  Command+e, required to type é on Mac, spawns the trigger/aliases/etc
  editor on a Mac. See
  http://forums.mudlet.org/viewtopic.php?f=9=3475=17119#p17119 for
  the original report.

  A solution could be to allow the Mudlet keybindings be customizable by
  the user.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1187176] Re: uninstallPackage() can fail to return

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/719

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 #719
   https://github.com/Mudlet/Mudlet/issues/719

** 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/1187176

Title:
  uninstallPackage() can fail to return

Status in Mudlet:
  Opinion

Bug description:
  uninstallPackage() can fail to return and none of the code after it
  will be run. Perhaps there is an error that happens that is not
  reported by Mudlet anywhere.  The following code, which accounts for
  this error:

  function svo_doupdate_click()
svo.updatelabel:echo([[Updating Svo...]])
svo.doupdatelabel:hide()
svo.dontupdatelabel:hide()

local name = svo.me.name

if not (uninstallPackage and installPackage) then
  svo.updatelabel:echo([[Can't update your Svo. You didn't update to Mudlet 2.1, and your 
current Mudlet lacks the features necessary. Go update first please.]])
  return
end

if not io.exists(getMudletHomeDir().."/svo/downloads/"..string.format("%s 
svo.zip", svo.me.name)) then
  svo.updatelabel:echo([[Hm, can't update Svo - seems the new system we downloaded 
dissapeared. Do 'vupdate force' to download it again.]])
  return
end

function svo_update_system()
  svo_updating_system = "uninstalling"
  uninstallPackage(name.." svo")

  svo_updating_system = "installing"
  svo.updatelabel:echo([[Uninstalled the old Svo, installing the new one now...]])
  installPackage(getMudletHomeDir().."/svo/downloads/"..string.format("%s 
svo.zip", svo.me.name))

  svo_updating_system = nil
  svo.echof("Svo updated! Restart Mudlet, and you'll be all done. You can 
find the changelog on svo.vadisystems.com.")

  svo.updatelabel:echo([[Svo updated!Restart Mudlet, and you'll be all done.]])
  svo.updatelabel:setStyleSheet([[
  margin: 0px;
  padding: 2px;

  /* Vertical gradient */
  background: qlineargradient(
  x1: 0, y1: 0, x2: 0, y2: 1,
  stop: 0 #3c3c3c, stop: 1 #232323
  );

  border: none;
  border-radius: 4px;

  color: #ff;

qproperty-alignment: 'AlignVCenter | AlignHCenter';
qproperty-wordWrap: true;
font-family: 'Ubuntu','Calibri',serif;
  ]])
end

svo_updating_system = "started"
tempTimer(10, function()
  if not svo_updating_system then return end

  if svo_updating_system == "uninstalling" then
svo.updatelabel:echo([[Hm, seems the update got stuck on the uninstallPackage() function. 
Try uninstalling Svo from the Package Manager and then installing it from the 
zip (found in ]].. getMudletHomeDir().."/svo/downloads/"..string.format("%s 
svo.zip", svo.me.name) ..[[) to upgrade now.]])
  elseif svo_updating_system == "installing" then
svo.updatelabel:echo([[Hm, seems the update got stuck on the installPackage() function. 
Old Svo is uninstalled, but it the new one didn't get installed - install your 
Svo zip (found in ]].. getMudletHomeDir().."/svo/downloads/"..string.format("%s 
svo.zip", svo.me.name) ..[[ via the Package Manager.]])
  end
end)
svo_update_system()
  end

  still has issues that people experience:

  Also this is the issue - Hm, seems the update got stuck on the 
uninstallPackage()function.
   Try uninstalling Svo from the package manager and then reinstalling it from 
the zip (found in 
  C:blahblah) to upgrade now.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1215042] Re: osx - UI not fully interactive until SLEEP occurs

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/735

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 #735
   https://github.com/Mudlet/Mudlet/issues/735

** 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/1215042

Title:
  osx - UI not fully interactive until SLEEP occurs

Status in Mudlet:
  Opinion

Bug description:
  I have been fighting with this problem on and off and recently I
  figured out what ultimately "fixes" the problem.

  The problem is that on a restart, with a freshly open Mudlet, the UI
  elements almost never properly respond to the mouse... even the
  buttons at the top to open editors and settings etc are unclickable...
  this happens until my laptop screen is closed and once everything
  wakes back up again... Mudlet is happy and works properly again.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1206459] Re: Text in miniconsoles on Mac is not antialiased

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/731

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 #731
   https://github.com/Mudlet/Mudlet/issues/731

** 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/1206459

Title:
  Text in miniconsoles on Mac is not antialiased

Status in Mudlet:
  Opinion

Bug description:
  See http://forums.mudlet.org/viewtopic.php?f=9=3552=17576#p17576
  for original problem report.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1209025] Re: mudlet stops working everytime I click on "maps"

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/732

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 #732
   https://github.com/Mudlet/Mudlet/issues/732

** 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/1209025

Title:
  mudlet stops working everytime I click on "maps"

Status in Mudlet:
  Opinion

Bug description:
  Mudlet stops working every time I click on map or download map script.
  my windows computer tells me mudlet.exe has stopped working and cannot
  download map script.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1215034] Re: save profile - less than ideal behavior

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/734

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 #734
   https://github.com/Mudlet/Mudlet/issues/734

** 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/1215034

Title:
  save profile - less than ideal behavior

Status in Mudlet:
  Opinion

Bug description:
  Recently my windows manager crashed and it seems despite having been
  running for several weeks, my latest changes to my mudlet scripts were
  not saved

  While i understand the "save profile" button solves this, it seems
  rather unintuitive that mudlet does not save the profile when you are
  making large changes to the triggers and such when you close the
  script window or when those triggers become active at least.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1676121] Re: Add an 'email me' download link for mobile site

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/715

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 #715
   https://github.com/Mudlet/Mudlet/issues/715

** Changed in: mudlet
   Status: Confirmed => Opinion

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

Title:
  Add an 'email me' download link for mobile site

Status in Mudlet:
  Opinion

Bug description:
  Idea taken from https://etcher.io - as Mudlet doesn't run on mobile
  devices, we should have a button where people can enter in their email
  to get a Mudlet download link sent to them, so they can download it
  when they get on their desktops.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1676744] Re: Investigate pcre_study for regex performance improvement

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/716

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 #716
   https://github.com/Mudlet/Mudlet/issues/716

** 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/1676744

Title:
  Investigate pcre_study for regex performance improvement

Status in Mudlet:
  Opinion

Bug description:
  http://www.pcre.org/original/doc/html/pcre_study.html looks useful to
  run on patterns after we save aliases/triggers.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1233106] Re: setLabelRightClickCallback() for triggering on right-clicks

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/699

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 #699
   https://github.com/Mudlet/Mudlet/issues/699

** 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/1233106

Title:
  setLabelRightClickCallback() for triggering on right-clicks

Status in Mudlet:
  Opinion

Bug description:
  See user request at
  http://forums.mudlet.org/viewtopic.php?f=5=92=360#p17888:

  > Can we get a setLabelRightClickCallback function, so we can have
  labels do something when you right click them?

  This opens up to the need for having a setLabelMiddleClickCallback,
  and then what do you do with many of the other buttons a mouse can
  have?

  It would be best to have a single function that reported which button
  was pressed - but unfortunately we can't tack it on as an argument to
  setLabelClickCallback because we already allow the user to pass an
  arbitrary amount of arguments, and doing anything else would stuff
  things up.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1579948] Re: User request for single log file that is appended rather than individual ones

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/704

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 #704
   https://github.com/Mudlet/Mudlet/issues/704

** 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/1579948

Title:
  User request for single log file that is appended rather than
  individual ones

Status in Mudlet:
  Opinion

Bug description:
  In http://forums.mudlet.org/viewtopic.php?f=5=5725 user Proxy
  expressed a desire for a single file that was appended to on each
  occasion rather than individual ones each time logging was started.
  Whilst this would be fairly trivial for the plain text file format I
  have reservations as to how easy it would be for the HTML form.  At
  present the style for each span is explicitly set in full detail at
  the start of that span, however I am aware from unreleased prototype
  code that if it were cached it would be possible to significantly
  reduce the size of HTML log files, particularly if only a few
  different styles are used repetitively through the entire log foil.
  If that were to be done it may be harder to maintain a single file
  that is appended unless we can overwrite it (to remove the closing
  HTML) and then re-parse the existing file to identify all previously
  used styles - it would not be impossible to do this but it may slow
  done the commencement of logging slightly IMHO.

  {This might a project I could attempt during my 2016 holiday in a few
  weeks if I need to take a break from I18n stuff!}

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1387868] Re: Unicode display in output

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/702

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 #702
   https://github.com/Mudlet/Mudlet/issues/702

** Changed in: mudlet
   Status: Confirmed => Opinion

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

Title:
  Unicode display in output

Status in Mudlet:
  Opinion

Bug description:
  People would like to be able to render Unicode in the output, for
  internalization and art purposes:
  http://www.mudlet.org/2014/10/mudlet-3-0-0-beta-
  preview-2/#comment-5935

  Will 3.0 bring any improvement/functionality to Mudlet being able to
  display unicode output from MU*s?

  This is a problem in any MU* that uses those characters, pretty much
  every non-English MU*, any MU* in which another player types them to
  you for so reason, and especially in fantasy MU*s that use the
  characters for accent/flavor purposes.

  It also ruins a lot of text ‘art’ and framing for things like built in
  maps that MU*s tend to output.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1221939] Re: Enable spellcheck in the composer

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/694

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 #694
   https://github.com/Mudlet/Mudlet/issues/694

** 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/1221939

Title:
  Enable spellcheck in the composer

Status in Mudlet:
  Opinion

Bug description:
  I frequently find myself copying texts from the composer window into
  an editor with spellcheck, finding a fair bit of typos within them. It
  would be nicer of Mudlet provided the spellcheck functionality in the
  composer.

  An ability to "learn" words is essential for this as well, as MUDs can
  invent new ones.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1233100] Re: creplace() - a replace with colour capabilities

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/698

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 #698
   https://github.com/Mudlet/Mudlet/issues/698

** 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/1233100

Title:
  creplace() - a replace with colour capabilities

Status in Mudlet:
  Opinion

Bug description:
  See user request at
  http://forums.mudlet.org/viewtopic.php?f=5=92=19054#p18144

  It would be really handy if there were a version of the replace
  function that could accept color codes, in the same way that cecho and
  cinsertText do.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1369186] Re: Z axis adjustment of elements

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/701

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 #701
   https://github.com/Mudlet/Mudlet/issues/701

** Changed in: mudlet
   Status: Incomplete => Opinion

-- 
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

Status in Mudlet:
  Opinion

Bug description:
  Feature request from a user to be able to change the Z axis level of
  labels and miniconsoles. At the moment, you can only set it during
  creation by way of creating one thing before another.

  Sent By: Sanaki on 9/13/4:47
  // From what I can see, QWidget::stackUnder(), QWidget::raise(), and 
QWidget::lower() accomplish that, though perhaps not quite as numerically as 
desired. The latter two would easily be usable in Mudlet though.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1233108] Re: A way to open a profile without connecting (offline profiles)

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/700

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 #700
   https://github.com/Mudlet/Mudlet/issues/700

** 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/1233108

Title:
  A way to open a profile without connecting (offline profiles)

Status in Mudlet:
  Opinion

Bug description:
  Connecting offline - just opening a profile - has been a long-time
  requested feature (april 2009:
  http://forums.mudlet.org/viewtopic.php?f=5=48, december 2009:
  http://forums.mudlet.org/viewtopic.php?t=1161#p2329, ..., august 2013:
  http://forums.mudlet.org/viewtopic.php?f=5=92=360#p17863)

  This can be fixed by adjusting the 'connect' option to have a little
  drop-down on its right side, spawning a menu that says 'Open profile
  offline'. It'll then load the profile but not initiate a MUD
  connection.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1233098] Re: Allow searchRoom() to accept search types

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/697

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 #697
   https://github.com/Mudlet/Mudlet/issues/697

** 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/1233098

Title:
  Allow searchRoom() to accept search types

Status in Mudlet:
  Opinion

Bug description:
  Going off the user suggestion at
  http://forums.mudlet.org/viewtopic.php?f=5=92=19054#p18722 and
  practical experience of having to filter searchRoom() results (or
  create own search function based off getRooms()), it would be really
  useful of searchRoom() accepted a second parameter that defined the
  search type - none for the default of substring, and then "perl regex"
  for perl regex, "exact match" for an exact match, "begin of line
  substring" and "substring".

  I'm not sure how to deal with cases yet - there will be times when you
  will not have exact case of the string you're searching for. Perhaps
  the perl regex search pattern with an (?i) will take care of it,
  though - might be better than introducing a third argument into the
  mix.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

[Mudlet-makers] [Bug 1224683] Re: A way to keep debug window open without debug info in the main window

[Vadim Peretokin]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/695

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 #695
   https://github.com/Mudlet/Mudlet/issues/695

** 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/1224683

Title:
  A way to keep debug window open without debug info in the main window

Status in Mudlet:
  Opinion

Bug description:
  User feedback: (Mudlet Clan): Ada says, "Is it possible to stop displaying 
system messages in the main output 
  window while the debug window is open?"

  Currently, we can't support this. But not being spammed with GMCP
  events when you want to debug your triggers sounds like a good idea.

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

___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp