Re: [Mudlet-makers] [Bug 918419] Re: gmcp hangs when dealing with a lot of items
This is not related to data compression. The bug is much worse. It affects the telnet state machine which needs to be patched to handle out-of-band data packages correctly, i.e. this bug affects ATCP, GMCP and MSDP if the packages are large enough. I've written a patch for GMCP a long time ago and I can post it by the end of next week when I get access to my stuff again, but ATCP and MSDP will need to get fixed the same way. Am 28.08.2014 12:05, schrieb Ahmed Charles: This is a bug with mudlet's decompression code for MCCP. Working on the fix. ___ 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
Re: [Mudlet-makers] [Bug 918419] Re: gmcp hangs when dealing with a lot of items
It's a severe bug. I've fixed it long time ago, but haven't pushed the code yet. Am 21.06.2014 16:14, schrieb Stephen Lyons: I'm getting some mojibake (after the processTelnetCommand: in lines containing that and also at the end of the same lines) when viewing posting: Vadim Peretokin (vperetokin) wrote on 2013-09-29. Maybe its not an issue but just the side effect of cut and pasting raw telnet byte sequences with characters with the high bit set (127) but is that the case or is something actually wrong there? ___ 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
Re: [Mudlet-makers] [Bug 1318256] [NEW] Serialization/deserialization issues
We need some affected profile xml files first./ /Am 11.05.2014 00:45, schrieb Vadim Peretokin: Public bug reported: 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=9t=4505p=20878#p20878 ** Affects: mudlet Importance: Undecided Status: New ___ 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
Re: [Mudlet-makers] [Bug 918419] Re: gmcp hangs when dealing with a lot of items
I'll try to make a hotfix release this weekend that only addresses the gmcp bug and nothing else. Am 28.04.2014 14:12, schrieb David: This is a huge issue in Aetolia currently and cause lockup, drop outs and freezing in pk ___ 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
Re: [Mudlet-makers] [Bug 1225591] Re: Blank spaces in an echo before text in trigger context are stripped
careful guys, this is not a bug but intentional behavior - git changes post 2.1 Am 27.01.2014 02:03, schrieb Chris: Fixed in mudlet/development ** Changed in: mudlet Status: Confirmed = Fix Committed ** Changed in: mudlet Assignee: (unassigned) = Chris (chrismudlet) -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1225591 Title: Blank spaces in an echo before text in trigger context are stripped Status in Mudlet the MUD client: Fix Committed Bug description: Steps to reproduce: make a new trigger put echo(\n hi\n hi) into it output will be: You see exits leading northeast, east (open door), west (open door), northwest, up, and down. hi hi Blank spaces before text in the echo are being stripped, and this is an undesirable modification - it breaks a lot of alignment in echoes. This is on current in git only and not 2.1. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1225591/+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
Re: [Mudlet-makers] [Bug 1193967] Re: 'Delete profile' disabled in latest git
The problem is that under certain circumstances a use of the delete button may delete a random profile :-) The delete button has been disabled until somebody analyzes the problem. Am 09.01.2014 15:37, schrieb Chris: Can someone provide a link to where this problem is described? -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1193967 Title: 'Delete profile' disabled in latest git Status in Mudlet the MUD client: Confirmed Bug description: This commit: http://sourceforge.net/p/mudlet/code/ci/bfaed1b67efa2e1c76cb2568a731dc71704e662c/tree/src/dlgConnectionProfiles.cpp?diff=666306cf16ab29983b740e4d6a314efb941eade5 introduced a bug which disables the 'Remove' button. if( profile.size() 1 ) return; Makes it so any profile which has a name greater than one character can't be deleted. Perhaps it is intended to be: if( profile.size() 1 ) return; Instead? To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1193967/+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
Re: [Mudlet-makers] [Bug 1256553] [NEW] Long command lines are not affected by client word wrapping
This is intentional because most people wanted to save screen space. To see the full command you can scroll back through your command list. Am 02.01.2014 16:48, schrieb A.W: My game does not wrap lines that are echoed solely to Mudlet. Sorry. That is the command echo feature of Mudlet which is not being word wrapped by Mudlet. Sorry you misunderstood. On Sat, Nov 30, 2013 at 2:58 PM, Vadim Peretokin vpereto...@gmail.comwrote: Mudlet does not wrap input text at all - it would be your game doing this. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1256553 Title: Long command lines are not affected by client word wrapping Status in Mudlet the MUD client: New 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
Re: [Mudlet-makers] [Bug 1248682] Re: Mudlet crashes when downloading a MMP map
crash in qt window creation code
Am 07.11.2013 09:00, schrieb Vadim Peretokin:
Full backtrace:
Thread 8 (Thread 0x7fffc2f98700 (LWP 25481)):
#0 0x742bca43 in __GI___poll (fds=optimised out, nfds=optimised
out, timeout=optimised out) at ../sysdeps/unix/sysv/linux/poll.c:87
resultvar = optimised out
oldtype = 0
result = optimised out
#1 0x7388bff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7388c124 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x75595314 in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /home/vadi/Programs/Qt5.1.1/5.1.1/gcc_64/lib/libQt5Core.so.5
No symbol table info available.
#4 0x75549b6b in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/home/vadi/Programs/Qt5.1.1/5.1.1/gcc_64/lib/libQt5Core.so.5
No symbol table info available.
#5 0x7537d272 in QThread::exec() () from
/home/vadi/Programs/Qt5.1.1/5.1.1/gcc_64/lib/libQt5Core.so.5
No symbol table info available.
#6 0x75381eb5 in ?? () from
/home/vadi/Programs/Qt5.1.1/5.1.1/gcc_64/lib/libQt5Core.so.5
No symbol table info available.
#7 0x74dade9a in start_thread (arg=0x7fffc2f98700) at
pthread_create.c:308
__res = optimised out
pd = 0x7fffc2f98700
now = optimised out
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {1, 1665595660221360907,
140737488335632, 140736464521664, 0, 3, -1665514240509924597,
-1665615151838188789}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0,
0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 0
pagesize_m1 = optimised out
sp = optimised out
freesize = optimised out
__PRETTY_FUNCTION__ = start_thread
#8 0x742c83fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
No locals.
#9 0x in ?? ()
No symbol table info available.
Thread 7 (Thread 0x7fffc3fff700 (LWP 25480)):
#0 0x742bca43 in __GI___poll (fds=optimised out, nfds=optimised
out, timeout=optimised out) at ../sysdeps/unix/sysv/linux/poll.c:87
resultvar = optimised out
oldtype = 0
result = optimised out
#1 0x7388bff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7388c124 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x75595314 in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /home/vadi/Programs/Qt5.1.1/5.1.1/gcc_64/lib/libQt5Core.so.5
No symbol table info available.
#4 0x75549b6b in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/home/vadi/Programs/Qt5.1.1/5.1.1/gcc_64/lib/libQt5Core.so.5
No symbol table info available.
#5 0x7537d272 in QThread::exec() () from
/home/vadi/Programs/Qt5.1.1/5.1.1/gcc_64/lib/libQt5Core.so.5
No symbol table info available.
#6 0x75381eb5 in ?? () from
/home/vadi/Programs/Qt5.1.1/5.1.1/gcc_64/lib/libQt5Core.so.5
No symbol table info available.
#7 0x74dade9a in start_thread (arg=0x7fffc3fff700) at
pthread_create.c:308
__res = optimised out
pd = 0x7fffc3fff700
now = optimised out
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {1, 1665595660221360907,
140737488338624, 140736481720768, 0, 3, -1665516494830884085,
-1665615151838188789}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0,
0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 0
pagesize_m1 = optimised out
sp = optimised out
freesize = optimised out
__PRETTY_FUNCTION__ = start_thread
#8 0x742c83fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
No locals.
#9 0x in ?? ()
No symbol table info available.
Thread 6 (Thread 0x7fffc9af3700 (LWP 25476)):
#0 0x742bca43 in __GI___poll (fds=optimised out, nfds=optimised
out, timeout=optimised out) at ../sysdeps/unix/sysv/linux/poll.c:87
resultvar = optimised out
oldtype = 0
result = optimised out
#1 0x7fffec3ec7cd in send_dg (resplen2=0x0, anssizp2=0x0, ansp2=0x0,
anscp=0x7fffc9af2020, gotsomewhere=synthetic pointer, v_circuit=synthetic
pointer, ns=0, terrno=0x7fffc9af0bc0, anssizp=0x7fffc9af0c50,
ansp=0x7fffc9af0b98, buflen2=0, buf2=0x0, buflen=32, buf=0x7fffc9af0c80
\246\027\001, statp=0x7fffc9af3db8) at res_send.c:1066
hp = 0x7fffc9af0c80
from = {sin6_family = 2, sin6_port = 13568, sin6_flowinfo =
16777343, sin6_addr = {__in6_u = {__u6_addr8 =
\000\000\000\000\000\000\000\000\340t\373\367\377\177\000, __u6_addr16 =
{0, 0, 0, 0, 29920, 63483, 32767, 0},
[Mudlet-makers] [Bug 918419] Re: gmcp hangs when dealing with a lot of items
I've started work on this. Fix is coming soon. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/918419 Title: gmcp hangs when dealing with a lot of items Status in Mudlet the MUD client: Confirmed Bug description: When dealing with a lot of individual items, your connection can look like its stuck: you don't receive any information back from the server and can't send anything. I found the problem on Achaea, and it only works when using gmcp. An easy way to simulate it would be the following: OUTR ALL KOLA (or whatever plant you have tons of) SPLIT KOLA INTO GROUPS OF 1 (do this till all your kola is split into individual items) COMBINE ALL KOLA This last step will cause the connection to hang. This is on an empty profile with only gmcp enabled. To confirm that this is a Mudlet-specific bug and not an Achaean one, I tried with another client (tintin++). With gmcp enabled there (and the Char, Room and Char.Items modules enabled), the combining worked. My Mudlet version is one compiled from git from a week or two ago, on Archlinux. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/918419/+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
Re: [Mudlet-makers] [Bug 1230143] [NEW] Non-complete artefact pipes priotization
wrong bug list I guess :-) Am 25.09.2013 10:17, schrieb Vadim Peretokin: Public bug reported: - 2013/09/25 01:01:49 - Mosr says, There isn't a way to make Svo prioritize an artie pipe for elm without manually setting the ID of it, is there? ** Affects: mudlet Importance: Wishlist Status: New -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1230143 Title: Non-complete artefact pipes priotization Status in Mudlet the MUD client: New Bug description: - 2013/09/25 01:01:49 - Mosr says, There isn't a way to make Svo prioritize an artie pipe for elm without manually setting the ID of it, is there? To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1230143/+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
Re: [Mudlet-makers] [Bug 1226558] [NEW] getRoom in TArea causes seg fault on map creation
No, I don't think so. Am 20.09.2013 16:24, schrieb Chris: Heiko, Do you have any uncommitted work to the mapper that would make this a waste of time to pursue at the moment? On Thu, Sep 19, 2013 at 5:45 PM, Vadim Peretokin vpereto...@gmail.comwrote: Yeah, I am in agreement there - I wouldn't go down the path of all in one. We could add it for conveniences sake - for example we have the all in one function to creating miniconsoles, but we also have the option of doing it step by step. However with Lua's ordered arguments (unless you're using tables, which does not make for an efficient API) then tacking everything to the end of a function becomes unwieldy. I've never used area 0 really. It's mostly annoying in the fact that it shows up in the list of areas the map has and in the mapper widget as a blank entry. I'd support hiding it from the API (partially - so we don't see it, but can use it) and the user (not showing in the mapper widget) and making use of it as the temporary void storage. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1226558 Title: getRoom in TArea causes seg fault on map creation Status in Mudlet the MUD client: New Bug description: Creating a new map with this code on the latest development branch causes this backtrace: 0 TArea::fast_ausgaengeBestimmen TArea.cpp 168 0x5128bb 1 TMap::setExit TMap.cpp304 0x5281ca 2 TLuaInterpreter::setExitTLuaInterpreter.cpp 6650 0x492075 3 ?? C:\mingw32\lib\lua51.dll0x66d862e0 4 ?? C:\mingw32\lib\lua51.dll0x66d8ffa6 5 ?? C:\mingw32\lib\lua51.dll0x66d866e0 6 ?? C:\mingw32\lib\lua51.dll0x66d81590 7 ?? C:\mingw32\lib\lua51.dll0x66d85ad6 8 ?? C:\mingw32\lib\lua51.dll0x66d86843 9 ?? C:\mingw32\lib\lua51.dll0x66d82870 10TLuaInterpreter::compileTLuaInterpreter.cpp 9649 0x49ce7a 11TScript::compileScript TScript.cpp 150 0x4b04d7 12TScript::setScript TScript.cpp 143 0x4b048e 13dlgTriggerEditor::saveScriptdlgTriggerEditor.cpp4282 0x456ad9 14dlgTriggerEditor::slot_saveScriptAfterEdit dlgTriggerEditor.cpp41780x456799 15dlgTriggerEditor::slot_save_editdlgTriggerEditor.cpp 69320x46a642 16dlgTriggerEditor::qt_static_metacallmoc_dlgTriggerEditor.cpp 509 0x57ecd9 17QMetaObject::activate qobject.cpp 34790x4c94cd0 18QMetaObject::activate qobject.cpp 33540x4c94672 19QAction::triggered moc_qaction.cpp 356 0x11674669 20QAction::activate qaction.cpp 11750x11673c1e ... More code: - -- Put your Lua functions here.-- -- -- -- Note that you can also use external Scripts -- - function makeMap() id = 0 for i=0,100 do for j=0, 100 do addRoom(id) --setRoomArea(id,0) --uncomment this and remove below call to avoid seg faults setRoomName(id, tostring(id)) setRoomCoordinates(id, i, j, 0) setExit(id-1,id,1) setExit(id,id-1,2) setRoomArea(id,0) id = id+1 end end end function makeLabels() id=1 for i=0,100 do for j=0, 100 do --display(id) x,y,z = getRoomCoordinates(id) createMapLabel(0,tostring(id),x,y,z,0,255,0,0,0,0) id = id+1 end end end --makeMap() --makeLabels() centerview(1) uncomment makeMap and it crashes. It fails when id is 1 as well, so it isn't because of the i-1 setExit bit. It's caused by mpRoomDB not being initialized because there is no area created. Even post creation, the room needs to be assigned to an area first before any calls to mpRoomDB are called, else it will seg fault. It seems like we need some 'void' area that has no name and is just an abyss for rooms waiting to be allocated to avoid breaking scripts. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1226558/+subscriptions -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1226558 Title: getRoom in TArea causes seg fault on map creation Status in Mudlet the MUD client: New Bug description
Re: [Mudlet-makers] [Bug 1226481] [NEW] deleteArea() doesn't have good performance
How large is the map (number of total rooms)? Am 17.09.2013 10:44, schrieb Vadim Peretokin: Public bug reported: On the attached map, deleteArea(255) took 10min+ (not exaggerating) on a 3.6Ghz machine, using latest git. The client locked up during this and was unusable. Is there any way this could be improved? ** Affects: mudlet Importance: Undecided Status: New ** Attachment added: map https://bugs.launchpad.net/bugs/1226481/+attachment/3825027/+files/map ** Description changed: On the attached map, deleteArea(255) took 10min+ (not exaggerating) on a - 3.6Ghz machine. The client locked up during this and was unusable. + 3.6Ghz machine, using latest git. The client locked up during this and + was unusable. Is there any way this could be improved? -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1226481 Title: deleteArea() doesn't have good performance Status in Mudlet the MUD client: New Bug description: On the attached map, deleteArea(255) took 10min+ (not exaggerating) on a 3.6Ghz machine, using latest git. The client locked up during this and was unusable. Is there any way this could be improved? To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1226481/+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
Re: [Mudlet-makers] [Bug 1225591] [NEW] Blank spaces in an echo before text in trigger context are stripped
The reason is that people wanted Mudlet to skip leading spaces when lines are being wrapped - some Achaea help text was unaligned and people claimed that all other clients wrap without leading spaces. As echo( 1\n 2\n) wraps the line after the first \n, this is the direct consequence. Am 15.09.2013 07:54, schrieb Vadim Peretokin: Public bug reported: Steps to reproduce: make a new trigger put echo(\n hi\n hi) into it output will be: You see exits leading northeast, east (open door), west (open door), northwest, up, and down. hi hi Blank spaces before text in the echo are being stripped, and this is an undesirable modification - it breaks a lot of alignment in echoes. This is on current in git only and not 2.1. ** Affects: mudlet Importance: Medium Status: Confirmed -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1225591 Title: Blank spaces in an echo before text in trigger context are stripped Status in Mudlet the MUD client: Confirmed Bug description: Steps to reproduce: make a new trigger put echo(\n hi\n hi) into it output will be: You see exits leading northeast, east (open door), west (open door), northwest, up, and down. hi hi Blank spaces before text in the echo are being stripped, and this is an undesirable modification - it breaks a lot of alignment in echoes. This is on current in git only and not 2.1. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1225591/+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
Re: [Mudlet-makers] [Bug 1225591] [NEW] Blank spaces in an echo before text in trigger context are stripped
There's only one type of wrapping in Mudlet and this applies to everything. Am 15.09.2013 12:38, schrieb Vadim Peretokin: Are you sure this didn't relate to Mudlets word wrapping of the MUDs text? I think that is what was the intention - when there is a long line and text is wrapped, spaces before it should be deleted. But it should not affect any of the scripting API. I remember now the issue was with help indexes - those do indeed look proper, now: CITY OF MHALDOR ambassador arenaeventsbehaviour bloodfeuds bounties branding catalogue citydirections cityfavours citylaws cityrepair combattournament creditsalesdragons eidolons Whereas before it looked like: CITY OF MHALDOR ambassador arenaeventsbehaviour bloodfeuds bounties branding catalogue citydirections cityfavourscitylaws cityrepair combattournament creditsalesdragons eidolons However this was not intended to affect the API and should not! -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1225591 Title: Blank spaces in an echo before text in trigger context are stripped Status in Mudlet the MUD client: Confirmed Bug description: Steps to reproduce: make a new trigger put echo(\n hi\n hi) into it output will be: You see exits leading northeast, east (open door), west (open door), northwest, up, and down. hi hi Blank spaces before text in the echo are being stripped, and this is an undesirable modification - it breaks a lot of alignment in echoes. This is on current in git only and not 2.1. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1225591/+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 1097004] Re: Fix or remove install support for Linux in qmake
install support removed ** Changed in: mudlet Status: New = 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/1097004 Title: Fix or remove install support for Linux in qmake Status in Mudlet the MUD client: Fix Released Bug description: We need to either remove install support in qmake completely, so 'make install' target does not get generated, or fix it, so it works right. It is causing problems with it in limbo - people try it, and think it's broken. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1097004/+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 1159570] Re: 'Save Profile As' doesn't preserve package relationships and configuration data
** Changed in: mudlet Importance: High = Wishlist -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1159570 Title: 'Save Profile As' doesn't preserve package relationships and configuration data Status in Mudlet the MUD client: New Bug description: 'Save Profile As' doesn't preserve package relationships and folders, so this cannot be used as a reliable way to move a profile between computers. Now that we have packages, I propose that 'save profile as' saves an xml that will keep the package relationships, and zip it all up along with the data in profiles/profile, so script settings would get saved as well. A special config.lua would indicate that this is a Mudlet backup and not a package, so upon extracting the folder levels will be done right and it wouldn't be considered a module or package. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1159570/+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 1097622] Re: Windows 2.1 Mudlet installer says claims it's 2.0
** Changed in: mudlet Status: New = 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/1097622 Title: Windows 2.1 Mudlet installer says claims it's 2.0 Status in Mudlet the MUD client: Fix Released Bug description: Windows 2.1 Mudlet installer says claims it's 2.0 in the titlebar and upon cancelling setup. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1097622/+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 1102328] Re: mudlet.h includes mudlet.h
** Changed in: mudlet Importance: Medium = Wishlist -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1102328 Title: mudlet.h includes mudlet.h Status in Mudlet the MUD client: New Bug description: mudlet.h includes mudlet.h. Harmless but an easy fix too. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1102328/+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 1128108] Re: Add command completion hook
** Changed in: mudlet Importance: Medium = Wishlist -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1128108 Title: Add command completion hook Status in Mudlet the MUD client: New Bug description: Please add hook/event/whatever that will allow to change how and what command completion can do. For example I would like to (after pressing tab) send a command to mud, wait for output, parse it and complete from that. Regards, Garagoth. Mudlet: 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1128108/+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 1092784] Re: Timers need tooltips
patch doesnt apply, plz recreate -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1092784 Title: Timers need tooltips Status in Mudlet the MUD client: In Progress Bug description: The fields of the Timer creation menu don't have tooltips, so it's hard to tell which number affects which time interval. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1092784/+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 1212574] Re: major bugs in mudlet-lua cinsert(), decho(), hecho()
test script (see screenshot for faulty output): echo(TEST PART1: C-API echo insert functions: blueSTARTINGlight_blue test#1green...\n) echo(redred textblueblue textgreenand some green text\n) moveCursor(10,getLineCount()-1) insertText(***INSERTING***orangeorangepinkpinkpurplepurple\ncontinuing on next line#1greentest 2\ncontinuing on next line#2bluetest3) cecho(\nTEST PART2: mudlet-lua cecho cinsert:blueSTARTINGlight_blue test#1green...\n) cecho(redred textblueblue textgreenand some green text\n) moveCursor(10,getLineCount()-1) cinsertText(***INSERTING***orangeorangepinkpinkpurplepurple\ncontinuing on next line#1greentest 2\ncontinuing on next line#2bluetest3) echo(\nRESULT: cinsert() doesn't respect inserted new lines\n) echo(TEST PART3: testing cecho() showing various bugs\n) cecho(red1Mudletgreen2Mudletblue3Mudlet\n) decho(255,100,1001Mudlet255,2,3:0,200,02Mudlet1,1,2003Mudlet\n) hecho(|cff00bb,000,Mudlet0|abc,aabbccMudlet|c00ffbb,aabbcc2Mudlet|c00bbffbbaaff3Mudlet\n) hecho(|cff00,000 documentation of hecho() needs to be changed to depend on double figure hex numbers\n) ** Changed in: mudlet Importance: Undecided = Critical -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1212574 Title: major bugs in mudlet-lua cinsert(), decho(), hecho() Status in Mudlet the MUD client: New Bug description: Bugs: 1. cinsert() doesn't process \n correctly 2. (!) line breaks in cecho() show but the line order is reversed (!) 3. problem in decho() compared to cecho() 2 4. hecho() documentation needs to be changed to only accept 3 8-bit double figure hex codes 00 instead of 000 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1212574/+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 1212574] [NEW] major bugs in mudlet-lua cinsert(), decho(), hecho()
Public bug reported: Bugs: 1. cinsert() doesn't process \n correctly 2. (!) line breaks in cecho() show but the line order is reversed (!) 3. problem in decho() compared to cecho() 2 4. hecho() documentation needs to be changed to only accept 3 8-bit double figure hex codes 00 instead of 000 ** Affects: mudlet Importance: Critical Status: New -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1212574 Title: major bugs in mudlet-lua cinsert(), decho(), hecho() Status in Mudlet the MUD client: New Bug description: Bugs: 1. cinsert() doesn't process \n correctly 2. (!) line breaks in cecho() show but the line order is reversed (!) 3. problem in decho() compared to cecho() 2 4. hecho() documentation needs to be changed to only accept 3 8-bit double figure hex codes 00 instead of 000 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1212574/+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
Re: [Mudlet-makers] [Bug 1212552] [NEW] Add an option for common replacements
People can easily make a script package anyways. Am 15.08.2013 08:11, schrieb Heiko Koehn: You'd need a language selector and really good implementations for various languages with special attention to the non-standard fictional character of most games - super difficult to make it so that it's not annoying (probably impossible) and certainly not with trivial regex patterns. Am 15.08.2013 09:51, schrieb Vadim Peretokin: Yes, they can turn it off if they don't like it, and if people really don't like it, we won't have it on by default. This is a client for humand and humans make typos, I find this feature to be nice actually. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1212552 Title: Add an option for common replacements Status in Mudlet the MUD client: New Bug description: I've been using Outlook for a bit, and I find the 'common replacements' feature to be fairly useful. I think we should have it as an option, defaulting to on. What this feature does is replace common mistakes on the fly - teh to the, [A-Z][A-Z][a-z]+ to [A-Z][a-z][a-z]+ and so on. We'd need a list of such replacements to make, so there's research to be done on compiling one. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1212552/+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
Re: [Mudlet-makers] [Bug 1201017] Re: Custom exit lines dialog broken in git
For the time being you can ignore any custom lines related isses as custum lines is still in the process of being reworked and completely unfinished at this point. Am 17.07.2013 11:39, schrieb Vadim Peretokin: I'm not getting the exits dialog at all on latest git. Here is a screencast. Do you see the same thing? ** Attachment added: No exits dialog.mp4 https://bugs.launchpad.net/mudlet/+bug/1201017/+attachment/3739754/+files/No%20exits%20dialog.mp4 -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1201017 Title: Custom exit lines dialog broken in git Status in Mudlet the MUD client: New Bug description: The custom exit lines dialog does not come up in current git, it goes straight to the line-making portion of the workflow. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1201017/+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
Re: [Mudlet-makers] [Bug 1095953] Re: Font spacing on Mac/Ubuntu/Win7+8 is a bit off
no issues with Qt4.8.2 either - also works fine with bitsteam sans mono Am 18.06.2013 20:24, schrieb Vadim Peretokin: I can confirm that this issue does not exhibit on Debian Sid (installed a VM to test). It uses Qt 4.8.4. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1095953 Title: Font spacing on Mac/Ubuntu/Win7+8 is a bit off Status in Mudlet the MUD client: New Bug description: See http://forums.mudlet.org/viewtopic.php?f=5t=3180p=15303#p15272 for explanation screenshots. The symptoms are similar on Ubuntu as well under Qt 4.8. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1095953/+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
Re: [Mudlet-makers] [Bug 1095953] Re: Font spacing on Mac/Ubuntu/Win7+8 is a bit off
summary: Windows: no problems Mac: slight problems using the OSX workaround. uncomment the osx workaround, rebuild and retest plz Linux: no problems on Debian. Ubuntu is using the exact same official Debian package, but there are problems - where are the differences in Debian and Ubuntu? The issue is most likely related to fontconfig/X package differences between the 2 distros. Which Qt version is being used on Ubuntu? Am 18.06.2013 20:30, schrieb Vadim Peretokin: Note that the Mudlet version in Debian Sid uses a different default font - it does not use Bitstream Vera Sans Mono. Debian Wheezy using test4, but again, using a different default font, did not exhibit this problem. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1095953 Title: Font spacing on Mac/Ubuntu/Win7+8 is a bit off Status in Mudlet the MUD client: New Bug description: See http://forums.mudlet.org/viewtopic.php?f=5t=3180p=15303#p15272 for explanation screenshots. The symptoms are similar on Ubuntu as well under Qt 4.8. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1095953/+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
Re: [Mudlet-makers] [Bug 1095953] Re: Font spacing on Mac/Ubuntu/Win7+8 is a bit off
What happens if you build against the qtsdk on both ubuntu systems? Am 16.06.2013 10:46, schrieb Vadim Peretokin: This issue does happen on Ubuntu 13.04. Note that you have to select the text in the minoconsole and move the selection back and forth, left to right, to see subtitle changes in the text placement to really observe this issue. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1095953 Title: Font spacing on Mac/Ubuntu/Win7+8 is a bit off Status in Mudlet the MUD client: New Bug description: See http://forums.mudlet.org/viewtopic.php?f=5t=3180p=15303#p15272 for explanation screenshots. The symptoms are similar on Ubuntu as well under Qt 4.8. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1095953/+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
Re: [Mudlet-makers] [Bug 1175316] Re: setBackgroundColor() on miniconsole causes a font change in main window
I can't reproduce this. Please close or provide reproduceable evidence. Am 16.06.2013 05:18, schrieb Vadim Peretokin: ** Changed in: mudlet Status: Invalid = New -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1175316 Title: setBackgroundColor() on miniconsole causes a font change in main window Status in Mudlet the MUD client: New Bug description: The following code triggers the font in the main window to change somewhat - you have to click on the main window or scroll to fix it back: createMiniConsole(test1,0,0,0,0) setBackgroundColor(test1,0,0,0,0) Original report: http://forums.mudlet.org/viewtopic.php?f=9t=3406p=16733#p16728 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1175316/+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
Re: [Mudlet-makers] [Bug 1095953] Re: Font spacing on Mac/Ubuntu/Win7+8 is a bit off
roomid? Am 16.06.2013 05:28, schrieb Vadim Peretokin: Here is a script for Achaea - go into wilderness and it'll show it. I'm not sure if it happens on win7/8, but are you saying you are dropping all support any OS that is not windows 7 or 8? ** Attachment added: wilderness map window.xml https://bugs.launchpad.net/mudlet/+bug/1095953/+attachment/3704745/+files/wilderness%20map%20window.xml -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1095953 Title: Font spacing on Mac/Ubuntu/Win7+8 is a bit off Status in Mudlet the MUD client: New Bug description: See http://forums.mudlet.org/viewtopic.php?f=5t=3180p=15303#p15272 for explanation screenshots. The symptoms are similar on Ubuntu as well under Qt 4.8. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1095953/+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
Re: [Mudlet-makers] [Bug 1128996] Re: 'Save Profile' doesn't backup the map
Save profile doesn't save the map. There's other buttons in the UI to do so. It's fixed with tooltips. Am 16.06.2013 06:33, schrieb Vadim Peretokin: How was this fixed if I could ask? 'Save profile' still doesn't make a map backup. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1128996 Title: 'Save Profile' doesn't backup the map Status in Mudlet the MUD client: Fix Released Bug description: 'Save Profile' doesn't backup the map, and it seems at least one user was misled into thinking that it does save the map, and lost work when Mudlet crashed. It should backup the map as it does the main profile. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1128996/+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
Re: [Mudlet-makers] [Bug 1095953] Re: Font spacing on Mac/Ubuntu/Win7+8 is a bit off
Can't see anything strange on Debian SID and latest git. Walked up a few room and then travelled south for some time. Looks all normal. Am 16.06.2013 09:02, schrieb Vadim Peretokin: 20386 and then ENTER WILDERNESS -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1095953 Title: Font spacing on Mac/Ubuntu/Win7+8 is a bit off Status in Mudlet the MUD client: New Bug description: See http://forums.mudlet.org/viewtopic.php?f=5t=3180p=15303#p15272 for explanation screenshots. The symptoms are similar on Ubuntu as well under Qt 4.8. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1095953/+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
Re: [Mudlet-makers] [Bug 1114588] Re: Custom exit lines should be possible to be added from scripts
Hi Chris, added this func with a few changes, here are a few comments: 1. line coordinates are of type qreal 2. direction/line relationship must be unique ([] instead of insert()) 3. valid directions should be anything including special exits (this feature needs to be added to the gui also) 4. getRoom(id) returns 0 if the room doesnt exist 5. I've added a func getCustomLines(roomid) that returns a table with all data. Maybe we change addCustonLine() to accept this kind of tables also to make scripting easier Heiko Am 11.06.2013 15:05, schrieb Chris: This branch: https://github.com/Chris7/Mudlet2/commits/exitRedesign custom exit lines commit: https://github.com/Chris7/Mudlet2/commit/8c38be9be026decf7b10b4d3c7bdcbc1fd304ac2 -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1114588 Title: Custom exit lines should be possible to be added from scripts Status in Mudlet the MUD client: Fix Committed Bug description: Please add possibility to add custom exit lines between two rooms using LUA scripts or possibility to connect rooms with special exits with visual lines on map. Currentlu GUI only version exists and even with that it is not possible to connect rooms, just draw a line that does move with rooms. Mudlet: 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1114588/+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
Re: [Mudlet-makers] [Bug 1095953] Re: Font spacing on Mac/Ubuntu/Win7+8 is a bit off
As long as I don't get a reproduceable case for win7/8 I ignore this issue. Am 11.06.2013 02:21, schrieb Vadim Peretokin: Here is another example of the spacing - and it being affected by highlights: http://i.imgur.com/oPguQuw.png?1 -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1095953 Title: Font spacing on Mac/Ubuntu/Win7+8 is a bit off Status in Mudlet the MUD client: New Bug description: See http://forums.mudlet.org/viewtopic.php?f=5t=3180p=15303#p15272 for explanation screenshots. The symptoms are similar on Ubuntu as well under Qt 4.8. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1095953/+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 1126575] Re: Buttons work in 50%
** Changed in: mudlet Status: New = Fix Released ** Changed in: mudlet Status: Fix Released = Incomplete ** Changed in: mudlet Status: Incomplete = Opinion ** Changed in: mudlet Status: Opinion = Invalid ** Changed in: mudlet Status: Invalid = Won't Fix ** Changed in: mudlet Status: Won't Fix = 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/1126575 Title: Buttons work in 50% Status in Mudlet the MUD client: Fix Released Bug description: I have created one button bar on top and added one button to it with a command. Button sends command to mud every second click on it, rest of clicks are just ignored. Stylesheet for button: not sure how it works, could not change even color of button using it It also seems that it is not possible to call lua script from button, which is very strange to me. Mudlet: 2.1 OS: Win 7 x64 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1126575/+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 1112223] Re: Package Exporter - Applies the /MudletPackage too early in the XML
looks like this has been merged already, plz verify ** Changed in: mudlet Status: Fix Committed = 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/1112223 Title: Package Exporter - Applies the /MudletPackage too early in the XML Status in Mudlet the MUD client: Fix Released Bug description: I created two seperate XMLs for small systems. Both inserted the /MudletPackage tag just after the Trigger package ended. When attempting to import those XMLs, mudlet never read and imported the Alias' or Scripts. Mudlet ver. 2.1 - Current Build OS X Mountain Lion To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1112223/+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 1163016] Re: handleWindowResize event fires before LuaGlobal
** Changed in: mudlet Status: New = 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/1163016 Title: handleWindowResize event fires before LuaGlobal Status in Mudlet the MUD client: Fix Released Bug description: The handleWindowResize event fires before LuaGlobal is initialized, spawning several errors in the errors view. A workable solution could be: define handleWindowResize() in the Lua state as soon as it is created in Mudlet. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1163016/+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 1153322] Re: Deleting mud ALSO deleted another mud's profile
bug fix desc: profile name of existing profiles cannot be changed the profile_name data field is set to read only except when adding a new profile. ** Changed in: mudlet Status: New = 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/1153322 Title: Deleting mud ALSO deleted another mud's profile Status in Mudlet the MUD client: Fix Released Bug description: I'm using the latest ubuntu 12.10. Mudlet 2.1. I've been using mudlet for a good while and not seen this bug. Last night I was trying new muds and I deleted from mudlet one that I added but didn't like--you know, where you have to type in the mud's name to confirm the delete. Well, I went on to play another mud at the same time opening a connection to my regular mud (God Wars II), and then soon quit Mudlet, ansering Yes, I wish to save the profile for the new mud and if it then when asked for God Wars, I _think_ I said yes. But answering No there shouldn't have been bad since I only connected to see who was on and made no oher changes. But, I'm not actually posistive if I connected to God Wars before or after deleting that other mud. Sorry. Anyway, upon later restarting Mudlet, God Wars II (my profile for it) was GONE. I clicked on the general profile for God Wars II and it did the whole download of new graphics pluggin and start with default settings. I went into the mudlet folder and only found the generic God Wars II profile there. My original profile for it was gone. So I lost all my triggers and aliases and settings for my original God Wars II profile. I can only asume that when I deleted that other mud I didn't like, Mudlet also deleted my God Wars profile as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1153322/+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 1097983] Re: Doors across area boundaries don't get drawn at proper locations
** Changed in: mudlet Status: Fix Committed = 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/1097983 Title: Doors across area boundaries don't get drawn at proper locations Status in Mudlet the MUD client: Fix Released Bug description: Doors across area boundaries don't get drawn at proper locations on the area boundary - instead they get drawn elsewhere in the area. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1097983/+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 1163444] Re: Mapper GUI doesn't match API functionality
** Changed in: mudlet Status: New = Incomplete ** Changed in: mudlet 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/1163444 Title: Mapper GUI doesn't match API functionality Status in Mudlet the MUD client: Fix Released Bug description: The API method setExit() will automatically remove exit stubs from a room for the directions being set. However, if a user uses the Mapper window GUI (via right-click-exits), the exit stubs are not correctly removed. Ideally, the Mapper GUI would honor the setExit() behavior as there is no GUI-accessible way to remove exit stubs otherwise short of deleting the room. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1163444/+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 1132260] Re: Perm triggers created after temp triggers run after temp triggers
For the time being I simply reorder the trigger list after package/module import. We can think about Chris's solution again when temp trigger priorities have been implemented, but for now this is much easier and won't cause any problems. ** Changed in: mudlet Status: Fix Committed = Won't Fix ** Changed in: mudlet Status: Won't Fix = 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/1132260 Title: Perm triggers created after temp triggers run after temp triggers Status in Mudlet the MUD client: Fix Released Bug description: Temp triggers normally run after perm triggers, however but not if the perm trigger was created later. For example, when you reinstall a package or a module, its perm triggers will be running after existing temp triggers. This creates an issue where perm triggers rely on the original MUD colors to do their work, which temp triggers later modify. If those perm triggers start running after temp triggers, they won't work. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1132260/+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 1094583] Re: map doesn't show rooms on area selection
commit link is not working -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1094583 Title: map doesn't show rooms on area selection Status in Mudlet the MUD client: Fix Committed Bug description: When an area is chosen, the user has to find the rooms, it should automatically bring the user to valid rooms. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1094583/+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 1097543] Re: setExitWeight() works on non-existent exits
** Changed in: mudlet Importance: Medium = High ** Changed in: mudlet Importance: High = Low -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1097543 Title: setExitWeight() works on non-existent exits Status in Mudlet the MUD client: New Bug description: setExitWeight() works on non-existent exits and remembers them - perhaps it shouldn't? To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1097543/+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 1174484] Re: Loss of Area specificness inTArea::getRoomsByPosition()
** Changed in: mudlet Status: New = 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/1174484 Title: Loss of Area specificness inTArea::getRoomsByPosition() Status in Mudlet the MUD client: Fix Released Bug description: Current (660) revision: Whilst researching for other TLuaInterpreter methods that were subject to the zero'th index problem mentioned in https://bugs.launchpad.net/mudlet/+bug/1173407 I discovered that TArea::getRoomsByPostion() was reporting rooms in ALL areas with the supplied x,y,z coordinates whereas when it is utilised by TLuaInterpreter::getRoomsByPostion() that method demands that it only returns rooms at the given coordinates in the area implicit in the call to the method. I have attached a short patch that seems to fix this issue, however because of the current state of my repository it might be a little fuzzy around the line numbers - I tweaked them by hand to fit the current code whereas I've dirtied my local copy a bit so I hope I got them right. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1174484/+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 1175316] Re: setBackgroundColor() on miniconsole causes a font change in main window
can't be reproduced - invalid ** Changed in: mudlet Status: Confirmed = Incomplete ** Changed in: mudlet Status: Incomplete = Opinion ** Changed in: mudlet Status: Opinion = Invalid -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1175316 Title: setBackgroundColor() on miniconsole causes a font change in main window Status in Mudlet the MUD client: Invalid Bug description: The following code triggers the font in the main window to change somewhat - you have to click on the main window or scroll to fix it back: createMiniConsole(test1,0,0,0,0) setBackgroundColor(test1,0,0,0,0) Original report: http://forums.mudlet.org/viewtopic.php?f=9t=3406p=16733#p16728 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1175316/+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
Re: [Mudlet-makers] [Bug 1098781] Re: Doors don't show up on exportAreaImage() in 2.1
released, but the whole func has to be ported to the new backend Am 06.06.2013 04:04, schrieb Chris: ** Changed in: mudlet Status: Fix Committed = Fix Released ** Changed in: mudlet Assignee: (unassigned) = Chris (chrismudlet) -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1098781 Title: Doors don't show up on exportAreaImage() in 2.1 Status in Mudlet the MUD client: Fix Released Bug description: Doors don't show up on exportAreaImage() in 2.1. See http://forums.mudlet.org/viewtopic.php?f=5t=3204sid=ba3bb3c8e46f85ed3340deb398544bf8p=15463#p15463 for original report. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1098781/+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
Re: [Mudlet-makers] [Bug 1185218] [NEW] HTML logging stops too early on it's own
No, sorry, I'm wrong. The loggin patch in 2.0 contained a logic error. Thing is fixed now. status - done Am 29.05.2013 02:34, schrieb Vadim Peretokin: Public bug reported: HTML logging seems to stop abruptly and too early without users doing it, still. See: http://forums.mudlet.org/viewtopic.php?f=5t=3358sid=2176036498284984f366be047d5c8897p=16945#p16945 ** Affects: mudlet Importance: Undecided Status: New -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1185218 Title: HTML logging stops too early on it's own Status in Mudlet the MUD client: New Bug description: HTML logging seems to stop abruptly and too early without users doing it, still. See: http://forums.mudlet.org/viewtopic.php?f=5t=3358sid=2176036498284984f366be047d5c8897p=16945#p16945 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1185218/+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 1183579] Re: 'Border background image' is not implemented
** Changed in: mudlet Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1183579 Title: 'Border background image' is not implemented Status in Mudlet the MUD client: New Bug description: 'Border background image' option in settings is not implemented. I think it should take a png/svg/whatever and just stretch it across the borders. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1183579/+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 1178490] Re: Map widget isn't come back after being closed by X
** Changed in: mudlet Importance: Undecided = Critical -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1178490 Title: Map widget isn't come back after being closed by X Status in Mudlet the MUD client: New Bug description: If you open the map as a widget and not an embedded console, and then close it with its small X button - toggling map again will not bring the widget up. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1178490/+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 1175316] Re: setBackgroundColor() on miniconsole causes a font change in main window
** Changed in: mudlet Importance: Undecided = Critical -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1175316 Title: setBackgroundColor() on miniconsole causes a font change in main window Status in Mudlet the MUD client: Confirmed Bug description: The following code triggers the font in the main window to change somewhat - you have to click on the main window or scroll to fix it back: createMiniConsole(test1,0,0,0,0) setBackgroundColor(test1,0,0,0,0) Original report: http://forums.mudlet.org/viewtopic.php?f=9t=3406p=16733#p16728 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1175316/+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 1173407] Re: getRoomsByPosition()'s table indexing starts at 0
** Changed in: mudlet Status: New = Won't Fix -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1173407 Title: getRoomsByPosition()'s table indexing starts at 0 Status in Mudlet the MUD client: Won't Fix Bug description: getRoomsByPosition()'s table indexing starts at 0, while it should be starting at 1. We would need to see if any public scripts are broken by this before fixing, if we can at all. All future functions should start their indexing at 1. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1173407/+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 1172031] Re: debugc() doesn't work
** Changed in: mudlet Importance: Undecided = Critical -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1172031 Title: debugc() doesn't work Status in Mudlet the MUD client: In Progress Bug description: debugc, defined as TLuaInterpreter::debug, is intended to allow you to write to the error console without breaking script execution - but it doesn't seem to be working. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1172031/+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 1170557] Re: Screen flashing issues on Snow Leopard
** Changed in: mudlet Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1170557 Title: Screen flashing issues on Snow Leopard Status in Mudlet the MUD client: New Bug description: A user is consistently having a screen flash issue, see video: https://dl.dropboxusercontent.com/u/16468573/Screen%20Recording%204.mov Happening on a 2011 macbook pro. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1170557/+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 1170749] Re: Typo in TRoom.h makes it impossible to change map west exit
** Changed in: mudlet
Status: New = Fix Committed
** Changed in: mudlet
Status: Fix Committed = 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/1170749
Title:
Typo in TRoom.h makes it impossible to change map west exit
Status in Mudlet the MUD client:
Fix Released
Bug description:
A mistake in line 63 of the current src/TRoom.h assigns a new west
exit to a room to the southwest position rather than the west one,
also making it impossible to remove a west exit. The fix is trivial
to correct I think :
diff a/src/TRoom.h b/src/TRoom.h
--- a/src/TRoom.h
+++ b/src/TRoom.h
@@ -58,11 +58,11 @@ public:
int getSouthwest() { return southwest; }
void setSouthwest( int id ) { southwest=id; }
int getSoutheast() { return southeast; }
void setSoutheast( int id ) { southeast=id; }
int getWest() { return west; }
-void setWest( int id ) { southwest=id; }
+void setWest( int id ) { west=id; }
int getEast() { return east; }
void setEast( int id ) { east=id; }
int getUp() { return up; }
void setUp( int id ) { up=id; }
int getDown() { return down; }
void setWest( int id ) { southwest=id; }
The blame(?) process seems to pin it to:
commit 4e651d55fd7a73af24fe66ae3d85e9e5b13a1fc5
Author: Heiko Koehn koehnhe...@googlemail.com Fri Mar 22 11:47:58
2013
safe mapper
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1170749/+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 1168987] Re: Pointer issue in TRoomDB.cpp:338 (Segfault)
** Changed in: mudlet Status: Fix Committed = 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/1168987 Title: Pointer issue in TRoomDB.cpp:338 (Segfault) Status in Mudlet the MUD client: Fix Released Bug description: As evidenced by: http://paste.ubuntu.com/5709118/ There seems to be a double deletion or deletion of a null pointer here. To resolve, the user is required to head into getMudletHomeDir() and remove any map related files and folders which is clearly very inconveniencing. I tried clearing things with: http://paste.ubuntu.com/5709132/ (Line 9 and 18). Although this is failing on the assertion. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1168987/+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 1166991] Re: MXP default link color should respect user preference for blue
Mudlet does not set link colors. The game choses the link color. ** Changed in: mudlet Status: New = Won't Fix -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1166991 Title: MXP default link color should respect user preference for blue Status in Mudlet the MUD client: Won't Fix Bug description: See http://forums.mudlet.org/viewtopic.php?f=5t=3204view=unread#p16508 for a use case. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1166991/+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 1170902] Re: permRegexTrigger/permSubstringTrigger doesn't set the name properly
** Changed in: mudlet
Status: Confirmed = 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/1170902
Title:
permRegexTrigger/permSubstringTrigger doesn't set the name properly
Status in Mudlet the MUD client:
Fix Released
Bug description:
For example:
permRegexTrigger(Prompt, , {^(\d+)h, (\d+)m}, [[health =
tonumber(matches[2]); mana = tonumber(matches[3])]])
permRegexTrigger(MapTriggerCapture, , {^(.*)$}, [[]])
Neither set the given name in the UI, they just set the number.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1170902/+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 1165993] Re: Profile navigation with keyboard doesn't work
** Changed in: mudlet Importance: Undecided = Low -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1165993 Title: Profile navigation with keyboard doesn't work Status in Mudlet the MUD client: New Bug description: Chagning currently selected profile through the direction keys doesn't actually load it's history, description and so on. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1165993/+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 1163016] Re: handleWindowResize event fires before LuaGlobal
** Changed in: mudlet Importance: Undecided = Critical -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1163016 Title: handleWindowResize event fires before LuaGlobal Status in Mudlet the MUD client: New Bug description: The handleWindowResize event fires before LuaGlobal is initialized, spawning several errors in the errors view. A workable solution could be: define handleWindowResize() in the Lua state as soon as it is created in Mudlet. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1163016/+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 1159570] Re: 'Save Profile As' doesn't preserve package relationships and configuration data
** Changed in: mudlet Importance: Undecided = High -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1159570 Title: 'Save Profile As' doesn't preserve package relationships and configuration data Status in Mudlet the MUD client: New Bug description: 'Save Profile As' doesn't preserve package relationships and folders, so this cannot be used as a reliable way to move a profile between computers. Now that we have packages, I propose that 'save profile as' saves an xml that will keep the package relationships, and zip it all up along with the data in profiles/profile, so script settings would get saved as well. A special config.lua would indicate that this is a Mudlet backup and not a package, so upon extracting the folder levels will be done right and it wouldn't be considered a module or package. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1159570/+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 1156914] Re: Mac Import Package dialog opens up behind Mudlet window
** Changed in: mudlet Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1156914 Title: Mac Import Package dialog opens up behind Mudlet window Status in Mudlet the MUD client: New Bug description: Mac Import Package dialog opens up behind Mudlet window / generally does not work well at all on certain machines. A possible workaround would be to use the native Objective-C dialogs instead of Qt's. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1156914/+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 1153322] Re: Deleting mud ALSO deleted another mud's profile
** Changed in: mudlet Importance: Undecided = Critical -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1153322 Title: Deleting mud ALSO deleted another mud's profile Status in Mudlet the MUD client: New Bug description: I'm using the latest ubuntu 12.10. Mudlet 2.1. I've been using mudlet for a good while and not seen this bug. Last night I was trying new muds and I deleted from mudlet one that I added but didn't like--you know, where you have to type in the mud's name to confirm the delete. Well, I went on to play another mud at the same time opening a connection to my regular mud (God Wars II), and then soon quit Mudlet, ansering Yes, I wish to save the profile for the new mud and if it then when asked for God Wars, I _think_ I said yes. But answering No there shouldn't have been bad since I only connected to see who was on and made no oher changes. But, I'm not actually posistive if I connected to God Wars before or after deleting that other mud. Sorry. Anyway, upon later restarting Mudlet, God Wars II (my profile for it) was GONE. I clicked on the general profile for God Wars II and it did the whole download of new graphics pluggin and start with default settings. I went into the mudlet folder and only found the generic God Wars II profile there. My original profile for it was gone. So I lost all my triggers and aliases and settings for my original God Wars II profile. I can only asume that when I deleted that other mud I didn't like, Mudlet also deleted my God Wars profile as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1153322/+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 1154978] Re: Search and other buttons go black
qt bug will fix automatically some day - ignore ** Changed in: mudlet Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1154978 Title: Search and other buttons go black Status in Mudlet the MUD client: New Bug description: Search and other buttons sometimes go completely black and only show when mouse is hovered on them. Confirmed on Ubuntu and Windows - attaching a Windows screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1154978/+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 1110941] Re: Ghost right-side border after hiding a button toolbar
** Changed in: mudlet Importance: Undecided = Low -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1110941 Title: Ghost right-side border after hiding a button toolbar Status in Mudlet the MUD client: New Bug description: Very rarely, when you hide a button toolbar there will be a border on the right side for the amount that the buttons covered left over. See screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1110941/+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 1146153] Re: Windows: complicated regex can crash Mudlet on a long line
not a mudlet bug
** Changed in: mudlet
Status: New = Won't Fix
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1146153
Title:
Windows: complicated regex can crash Mudlet on a long line
Status in Mudlet the MUD client:
Won't Fix
Bug description:
The following regex: ^(?:[A-Za-z]+\b,? *){2,} tells you, That looks
good\. I'll be in touch\.
Will crash Windows Mudlet on a really, really long line from the game
(presumably to an overflow, there are over 4k frames on the backtrace
when it happens). Doesn't happen on 64bit Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1146153/+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 1099688] Re: does not resolve the \t character
** Changed in: mudlet Status: New = Fix Committed ** Changed in: mudlet Status: Fix Committed = 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/1099688 Title: does not resolve the \t character Status in Mudlet the MUD client: Fix Released Bug description: Mudlet does not seem to support the \t character (tab). On muds where this is used, Mudlet prints nothing. It does not indent at all. What is expected is either showing the tab character or 8 spaces, but neither happens, and things that are aligned using tabs make things look all wonky, like maps, etc. Mudlet: 2.1 OS: OSX 10.8.2 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1099688/+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 1143209] Re: Allow only foreground or only background in color triggers
** Changed in: mudlet Importance: Undecided = High -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1143209 Title: Allow only foreground or only background in color triggers Status in Mudlet the MUD client: New Bug description: Color triggers right now enforce a foreground *and* a background color. If the user changes their default Mudlet background color to a custom one, both triggers that only want the foreground color will fail, and it will be impossible to adjust them to the custom color as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1143209/+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 1136265] Re: registered event handler add/remove not functioning properly
** Changed in: mudlet Importance: Undecided = Low -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1136265 Title: registered event handler add/remove not functioning properly Status in Mudlet the MUD client: New Bug description: Using Mudlet 2.1 OS is Windows 7 Home Premium, 64bit If I remove ALL registered event handlers via clicking the remove event handler from list button, I am unable to add an event via Add User Defined Event Handler prompt. The problem resolves itself if I click on a different script or script folder but this is very inconvenient. Here's a video of the problem: http://youtu.be/vfoIIABEXhc To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1136265/+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 1097953] Re: mudlet won't allow me to paste text being copied from an outside program
** Changed in: mudlet Status: New = Invalid -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1097953 Title: mudlet won't allow me to paste text being copied from an outside program Status in Mudlet the MUD client: Invalid Bug description: So here's my problem: if I am in mudlet (using version 2.1) and on Windows 7 x64, I can copy and paste text just fine, both pasting to mudlet and to outside programs, however when I copy text, for example a URL in google chrome, and try to paste it into mudlet, it acts as if nothing is copied. However, if I then go to notepad and paste, it will paste just fine. I know a few others who have the same issue...I'd really like to see this getting fixed, it's greatly hindering my ability to do my job on Aetolia. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1097953/+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 1128996] Re: 'Save Profile' doesn't backup the map
** Changed in: mudlet Importance: Medium = Critical -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1128996 Title: 'Save Profile' doesn't backup the map Status in Mudlet the MUD client: Fix Committed Bug description: 'Save Profile' doesn't backup the map, and it seems at least one user was misled into thinking that it does save the map, and lost work when Mudlet crashed. It should backup the map as it does the main profile. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1128996/+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 1126575] Re: Buttons work in 50%
** Changed in: mudlet Importance: Medium = Critical -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1126575 Title: Buttons work in 50% Status in Mudlet the MUD client: New Bug description: I have created one button bar on top and added one button to it with a command. Button sends command to mud every second click on it, rest of clicks are just ignored. Stylesheet for button: not sure how it works, could not change even color of button using it It also seems that it is not possible to call lua script from button, which is very strange to me. Mudlet: 2.1 OS: Win 7 x64 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1126575/+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
Re: [Mudlet-makers] [Bug 1184124] [NEW] Pathfinder choosing longer paths
Exits may be locked? Otherwise you need to send me the map file, speedwalk script and server/login details of your game. Am 25.05.2013 13:09, schrieb Garagoth: Public bug reported: Mudlet: 2.1 OS: Win 7 I have a city map with many alternative communication paths. All exits have the same exit weight, all rooms are created equal. When I double-click on target location and speedwalk kicks in, it chooses really weird paths - usually not the shortest one. Path one way: se, s, sw, e, e, e, ne, n, nw, nw, w, ne, ne, e, e, ne, nw, n, w, w, nw, nw, w, w, w, w Return path: sw, sw, se, se, e, e, s, s, s, se Attached is a screenshot of map. Locations in green circles are start and destination location. P.S. A context menu on map export area to image would be nice. ** Affects: mudlet Importance: Undecided Status: New ** Tags: pathfinder ** Attachment added: map_olgrion.png https://bugs.launchpad.net/bugs/1184124/+attachment/3686417/+files/map_olgrion.png -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1184124 Title: Pathfinder choosing longer paths Status in Mudlet the MUD client: New Bug description: Mudlet: 2.1 OS: Win 7 I have a city map with many alternative communication paths. All exits have the same exit weight, all rooms are created equal. When I double-click on target location and speedwalk kicks in, it chooses really weird paths - usually not the shortest one. Path one way: se, s, sw, e, e, e, ne, n, nw, nw, w, ne, ne, e, e, ne, nw, n, w, w, nw, nw, w, w, w, w Return path: sw, sw, se, se, e, e, s, s, s, se Attached is a screenshot of map. Locations in green circles are start and destination location. P.S. A context menu on map export area to image would be nice. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1184124/+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 1124802] Re: Rooms are not properly removed on map load
** Changed in: mudlet Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1124802 Title: Rooms are not properly removed on map load Status in Mudlet the MUD client: Invalid Bug description: When you load a new map in, current rooms are not properly removed first. This leads to an issue where if a room was deleted in a new map and you load it, it will not get painted, but it will exist - and show up in searchRoom, and roomExists will say it still exists. For a short demo, import the map with non-deleted room.dat map, and then import the map with deleted room.dat map in that order. You'll see that room 4855 was deleted, however it still shows up in searchRooms (causing problems) and roomExists(4855) will say true for it. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1124802/+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 1117858] Re: Syntax errors inside setLink code can get shown on the wrong profile
** Changed in: mudlet Status: Fix Committed = 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/1117858 Title: Syntax errors inside setLink code can get shown on the wrong profile Status in Mudlet the MUD client: Fix Released Bug description: Syntax errors inside setLink code can get shown on the wrong profile. For example, I had 2 tabs open, and was working with setLink in one of them. When setLink code had a syntax error in it, nothing showed up in the errors view - however on the main screen of another, completely unrelated profile, the error messages were showing up in white. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1117858/+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 1092769] Re: Event handlers can go off multiple times
** Changed in: mudlet Status: Fix Committed = 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/1092769 Title: Event handlers can go off multiple times Status in Mudlet the MUD client: Fix Released Bug description: Event handlers can somehow get into a state where they will consistently go off more than once. In an example I've got, on one profile run one event handler is going off 8 times, and another 144 times (!). Just raising the event makes it go off all those times, consistently, until you restart Mudlet. I haven't quite worked out what is causing this issue just yet, either - this needs to be narrowed down. It does happen to everyone somewhat infrequently however all the way from test4 and before. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1092769/+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 1133023] Re: line wrap of echo in trigger context
** Changed in: mudlet Status: New = 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/1133023 Title: line wrap of echo in trigger context Status in Mudlet the MUD client: Fix Released Bug description: function box() echo(\nusing echo():\n) echo(**\n) echo(**..string.rep( , 62)..**\n) echo(**\n) end wrong line wrap in trigger context unless line wrap is increased to a higher value than 2 line lengths To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1133023/+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
Re: [Mudlet-makers] [Bug 1168987] Re: Pointer issue in TRoomDB.cpp:338 (Segfault)
OK thx Am 15.04.2013 02:11, schrieb Martin Tee: ** Description changed: As evidenced by: http://paste.ubuntu.com/5709118/ There seems to be a double deletion or deletion of a null pointer here. - To resolve, the user is required to head into getMudletHomeDir() and remove any map related files and folders which is clearly very inconveniencing. + To resolve, the user is required to head into getMudletHomeDir() and remove any map related files and folders which is clearly very inconveniencing. I tried clearing things with: http://paste.ubuntu.com/5709132/ + (Line 9 and 18). Although this is failing on the assertion. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1168987 Title: Pointer issue in TRoomDB.cpp:338 (Segfault) Status in Mudlet the MUD client: New Bug description: As evidenced by: http://paste.ubuntu.com/5709118/ There seems to be a double deletion or deletion of a null pointer here. To resolve, the user is required to head into getMudletHomeDir() and remove any map related files and folders which is clearly very inconveniencing. I tried clearing things with: http://paste.ubuntu.com/5709132/ (Line 9 and 18). Although this is failing on the assertion. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1168987/+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
Re: [Mudlet-makers] [Bug 1168987] Re: Pointer issue in TRoomDB.cpp:338 (Segfault)
fixed Am 15.04.2013 02:11, schrieb Martin Tee: ** Description changed: As evidenced by: http://paste.ubuntu.com/5709118/ There seems to be a double deletion or deletion of a null pointer here. - To resolve, the user is required to head into getMudletHomeDir() and remove any map related files and folders which is clearly very inconveniencing. + To resolve, the user is required to head into getMudletHomeDir() and remove any map related files and folders which is clearly very inconveniencing. I tried clearing things with: http://paste.ubuntu.com/5709132/ + (Line 9 and 18). Although this is failing on the assertion. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1168987 Title: Pointer issue in TRoomDB.cpp:338 (Segfault) Status in Mudlet the MUD client: New Bug description: As evidenced by: http://paste.ubuntu.com/5709118/ There seems to be a double deletion or deletion of a null pointer here. To resolve, the user is required to head into getMudletHomeDir() and remove any map related files and folders which is clearly very inconveniencing. I tried clearing things with: http://paste.ubuntu.com/5709132/ (Line 9 and 18). Although this is failing on the assertion. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1168987/+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
Re: [Mudlet-makers] [Bug 1166930] Re: Cannot turn MXP off
I'm afraid but it's impossible because it's a server but, not ours. If we don't negotiate MXP the server shouldn't use it. If we ignore MXP on our end i.e. not strip MXP tags and escape sequences, the user won't be able to read anything within the MXP spam. However, we can add an option for MXP link color selection. Am 11.04.2013 00:39, schrieb Vadim Peretokin: Would it be possible to have the MXP engine ignore and strip out MXP without too much effort/slowdown? It would be better for the option to go all the way through. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1166930 Title: Cannot turn MXP off Status in Mudlet the MUD client: New Bug description: Bug Report: mudlet 2.1, latest Ubuntu Selecting 'Force MXP Negotiantions OFF' in mudlet-settings-special options DOES NOT turn MXP off. You can test this by turning it off, saving and then re-connecting to God Wars II for example. I've tried to get it to turn off for The 7th Plane at 209.90.73.150 . Screenshot http://imgur.com/8g2PEom The reason I wanted it off was because I can't change the MXP link colors and there's a dark blue that is used that I cannot read on my laptop. I can change the blue in mudlet view color prefs but that doesn't affect MXP link colors. Codrus To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1166930/+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
Re: [Mudlet-makers] [Bug 1166930] [NEW] Cannot turn MXP off
This isn't a Mudlet but, but an MXP standard shortcoming. Mostly you can turn off MXP with some specific game command. MXP-off Mudlet option just means that Mudlet tries to not enable MXP on connect. Am 09.04.2013 19:53, schrieb Tom Grey: Public bug reported: Bug Report: mudlet 2.1, latest Ubuntu Selecting 'Force MXP Negotiantions OFF' in mudlet-settings-special options DOES NOT turn MXP off. You can test this by turning it off, saving and then re-connecting to God Wars II for example. I've tried to get it to turn off for The 7th Plane at 209.90.73.150 . Screenshot http://imgur.com/8g2PEom The reason I wanted it off was because I can't change the MXP link colors and there's a dark blue that is used that I cannot read on my laptop. I can change the blue in mudlet view color prefs but that doesn't affect MXP link colors. Codrus ** Affects: mudlet Importance: Undecided Status: New -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1166930 Title: Cannot turn MXP off Status in Mudlet the MUD client: New Bug description: Bug Report: mudlet 2.1, latest Ubuntu Selecting 'Force MXP Negotiantions OFF' in mudlet-settings-special options DOES NOT turn MXP off. You can test this by turning it off, saving and then re-connecting to God Wars II for example. I've tried to get it to turn off for The 7th Plane at 209.90.73.150 . Screenshot http://imgur.com/8g2PEom The reason I wanted it off was because I can't change the MXP link colors and there's a dark blue that is used that I cannot read on my laptop. I can change the blue in mudlet view color prefs but that doesn't affect MXP link colors. Codrus To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1166930/+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
Re: [Mudlet-makers] [Bug 1163444] Re: Mapper GUI doesn't match API functionality
This looks *very* good and it's clearly an important improvement.
Am 03.04.2013 05:06, schrieb Stephen Lyons:
If this is the same Room Exits GUI that has Text Line edit boxes for
normal directional exits and buttons for each that Lock to prevent
*editing* those same Text Line edit boxes at the same time as they set
the feature to prevent the route finding code from using that exit - as
the API lockExit() function does then I may be able to assist.
Sorry if this is a bit dense:
I have made some progress working over the GUI dialogue box and associated
code to draw all the exit control functions together:
* exit stubs and validated exit entry (also color coded to indicate validity
as the digits are entered) - mutual exclusivity is enforced;
* exit locking and spin-boxes (0-) for exit weighting {though given that
a locked exit is effectively an infinite room weighting we could code the
former as a -1 value to the latter}
* radio buttons to set/clear door markers
* a centrally place indicator to show the number of the room that is being
EDITed!
* tool-tips to guide the user + an a disabled, dummy copy of the controls for
one exit enlarged to accommodate the labels that would otherwise be
redundantly duplicated and make larger the controls for each exit.
I had enforced mutual exclusivity for the other controls with stub exits
but I realise that in practice one is perfectly likely to find a locked
door without knowing what is on the other side so the door marker
control at least should be enabled for either a stub exit OR a valid
exit.
In testing I have found that the 2DMap drawing code attempts to draw
stub/normal exits for the up/down/in/out directions but fails for the
latter pair to single centrally placed thin horizontal line - I've hand
bodged the code to draw a small (about 2/3rd the size) pair of inward
pointing triangle for in that sits in the space left and right of the
points of the up and down exit indicators and a slightly larger
outward pointing pair on the outside of these for out. They, like the
up/down pair are hollow for stubs and filled in for real exits. May
I suggest that someone a bit better at the coordinate number juggling
looks that bit of code over - what I propose is only a suggestion but it
visually fits.
I also had left out controls for door symbols for the
up/down/in/out but I had subsequently thought that we could
change the brush colour used to fill-in the symbols to match the
colours used for the xy-plane ones - retaining the black outline though
so that they still show up on any room that has its environment set to a
colour that matches one of the door colours. Humm, that would not work
for a stub exit with a marker door though ...
I've held off on further tweaking here as Heiko suggests there is some
revision to the mapper coming through shortly but I think there are some
more things that need work: the Special exit part - needs another column
for exit weighting the special exits, unless we combine it with the exit
locking. Do we need the ability to set door symbols on exits drawn with
custom exit lines, could put the marker on the first line from the room,
in which case we can add them also to Special Exits.
OK that's enough from me for the moment.
** Attachment added: Replacement Exit Dialogue box - work so far
https://bugs.launchpad.net/mudlet/+bug/1163444/+attachment/3616553/+files/Screenshot-Exit%20details%20for%20room.png
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1163444
Title:
Mapper GUI doesn't match API functionality
Status in Mudlet the MUD client:
New
Bug description:
The API method setExit() will automatically remove exit stubs from a
room for the directions being set. However, if a user uses the Mapper
window GUI (via right-click-exits), the exit stubs are not correctly
removed.
Ideally, the Mapper GUI would honor the setExit() behavior as there is
no GUI-accessible way to remove exit stubs otherwise short of deleting
the room.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1163444/+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 1164804] Re: Exit lines don't 'anchor' to exit direction
@ Stephen Your example clearly shows that the current setup is lacking when a game doesn't sync a door between 2 rooms correctly. The drawing code, must ensure, however, that all exit lines are actually drawn. The current drawing routine is explicitly slow and sports zero speed optimizations because it's still unclear what features are actually needed because too few MUDs have good mapper scripts. There's lots of room for improvements once the new mapper backend is out. @ Daagar You are supposed to use custom lines for geographically illogical standard exit lines. Custom lines have the exact feature you're looking for. ** Changed in: mudlet Status: New = Invalid -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1164804 Title: Exit lines don't 'anchor' to exit direction Status in Mudlet the MUD client: Invalid Bug description: Mudlet 2.1, Win7 x64 Visual issue in the mapper: Consider two rooms connected east-west. If I move the room to the east 'below' the room to the west, I would expect the connection between them to visually be a 'Z' shape, where it is obvious that the exits still extend from the east and west respectively. Instead, the lines originate from the center of a room. So if I move the east-west pair as above, the exit line will visually appear as if it extends from the south/north. The exit lines should potentially be drawn between the ends of the 'exit stubs', rather from the center of a room. In the example above, this would give the expected 'Z' shape. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1164804/+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
Re: [Mudlet-makers] [Bug 1163016] [NEW] handleWindowResize event fires before LuaGlobal
This has been fixed a long time ago. Looks like a regression. Am 01.04.2013 23:45, schrieb Vadim Peretokin: Public bug reported: The handleWindowResize event fires before LuaGlobal is initialized, spawning several errors in the errors view. A workable solution could be: define handleWindowResize() in the Lua state as soon as it is created in Mudlet. ** Affects: mudlet Importance: Undecided Status: New -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1163016 Title: handleWindowResize event fires before LuaGlobal Status in Mudlet the MUD client: New Bug description: The handleWindowResize event fires before LuaGlobal is initialized, spawning several errors in the errors view. A workable solution could be: define handleWindowResize() in the Lua state as soon as it is created in Mudlet. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1163016/+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
Re: [Mudlet-makers] [Bug 1163016] [NEW] handleWindowResize event fires before LuaGlobal
I know for sure that I registered an empty function in TLuaInterpreter Am 08.04.2013 10:23, schrieb Vadim Peretokin: It's not a regression. It was never fixed and still happens. You cannot fix this in LuaGlobal when the event fires before LuaGlobal is loaded, I think... -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1163016 Title: handleWindowResize event fires before LuaGlobal Status in Mudlet the MUD client: New Bug description: The handleWindowResize event fires before LuaGlobal is initialized, spawning several errors in the errors view. A workable solution could be: define handleWindowResize() in the Lua state as soon as it is created in Mudlet. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1163016/+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
Re: [Mudlet-makers] [Bug 1163016] [NEW] handleWindowResize event fires before LuaGlobal
Just had a look at the code: The thing never got merged :( Am 08.04.2013 10:23, schrieb Vadim Peretokin: It's not a regression. It was never fixed and still happens. You cannot fix this in LuaGlobal when the event fires before LuaGlobal is loaded, I think... -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1163016 Title: handleWindowResize event fires before LuaGlobal Status in Mudlet the MUD client: New Bug description: The handleWindowResize event fires before LuaGlobal is initialized, spawning several errors in the errors view. A workable solution could be: define handleWindowResize() in the Lua state as soon as it is created in Mudlet. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1163016/+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
Re: [Mudlet-makers] [Bug 1164804] Re: Exit lines don't 'anchor' to exit direction
So you're talking about map editor visual effects when editing rooms? Am 08.04.2013 17:14, schrieb daagar: Custom exit lines are not the answer here. There is nothing geographically illogical about rooms connected east to west as in the example. The fact that the user drags the rooms around to any other configuration should not change the visual appearance that the rooms are connected from the east side of one room to the west side of the other. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1164804 Title: Exit lines don't 'anchor' to exit direction Status in Mudlet the MUD client: Invalid Bug description: Mudlet 2.1, Win7 x64 Visual issue in the mapper: Consider two rooms connected east-west. If I move the room to the east 'below' the room to the west, I would expect the connection between them to visually be a 'Z' shape, where it is obvious that the exits still extend from the east and west respectively. Instead, the lines originate from the center of a room. So if I move the east-west pair as above, the exit line will visually appear as if it extends from the south/north. The exit lines should potentially be drawn between the ends of the 'exit stubs', rather from the center of a room. In the example above, this would give the expected 'Z' shape. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1164804/+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
Re: [Mudlet-makers] [Bug 1164804] Re: Exit lines don't 'anchor' to exit direction
No, the exit drawing code for *custom lines* isn't agnostic about directions and does exactly what daagar is after imho - if I understand him correctly. Am 08.04.2013 18:30, schrieb Stephen Lyons: The 2D map drawing is actually agnostic about the name or command for orthogonal exits which means that implementing code that would, say, draw half a line in the right direction for the exits for each room such that they would line up for two adjacent rooms in the right physical placement and then link the end of those lines if they are NOT in adjacent correct positions means more than a trivial revision to the (rev 658) code. :( I'm just reviewing 659 so can't comment on that yet. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1164804 Title: Exit lines don't 'anchor' to exit direction Status in Mudlet the MUD client: Invalid Bug description: Mudlet 2.1, Win7 x64 Visual issue in the mapper: Consider two rooms connected east-west. If I move the room to the east 'below' the room to the west, I would expect the connection between them to visually be a 'Z' shape, where it is obvious that the exits still extend from the east and west respectively. Instead, the lines originate from the center of a room. So if I move the east-west pair as above, the exit line will visually appear as if it extends from the south/north. The exit lines should potentially be drawn between the ends of the 'exit stubs', rather from the center of a room. In the example above, this would give the expected 'Z' shape. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1164804/+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
Re: [Mudlet-makers] [Bug 1164804] Re: Exit lines don't 'anchor' to exit direction
Am 08.04.2013 19:32, schrieb Chris: Having to draw a custom exit line for these scenarios is not a good solution as compared to just having the visual equivalent of connecting the ends of exit stubs as opposed to connecting room centers. Given the mapper is getting some overhauls now, I'll use this as a chance to optimize simply the exit drawing code as well. OK -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1164804 Title: Exit lines don't 'anchor' to exit direction Status in Mudlet the MUD client: Invalid Bug description: Mudlet 2.1, Win7 x64 Visual issue in the mapper: Consider two rooms connected east-west. If I move the room to the east 'below' the room to the west, I would expect the connection between them to visually be a 'Z' shape, where it is obvious that the exits still extend from the east and west respectively. Instead, the lines originate from the center of a room. So if I move the east-west pair as above, the exit line will visually appear as if it extends from the south/north. The exit lines should potentially be drawn between the ends of the 'exit stubs', rather from the center of a room. In the example above, this would give the expected 'Z' shape. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1164804/+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
Re: [Mudlet-makers] [Bug 1132260] Re: Perm triggers created after temp triggers run after temp triggers
Put this in a seperate branch plz to not make your repo incompatible. Am 11.03.2013 21:07, schrieb Chris: Tested briefly, works. https://github.com/Chris7/Mudlet2/commit/f721b21fb086873611fab163ef44d001d1922e72 ** Changed in: mudlet Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1132260 Title: Perm triggers created after temp triggers run after temp triggers Status in Mudlet the MUD client: Fix Committed Bug description: Temp triggers normally run after perm triggers, however but not if the perm trigger was created later. For example, when you reinstall a package or a module, its perm triggers will be running after existing temp triggers. This creates an issue where perm triggers rely on the original MUD colors to do their work, which temp triggers later modify. If those perm triggers start running after temp triggers, they won't work. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1132260/+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
Re: [Mudlet-makers] [Bug 1132260] Re: Perm triggers created after temp triggers run after temp triggers
We could use this branch to add trigger priorities for tempTriggers efficiently, but this branch clearly needs extensive testing before we can merge it. Am 11.03.2013 21:07, schrieb Chris: Tested briefly, works. https://github.com/Chris7/Mudlet2/commit/f721b21fb086873611fab163ef44d001d1922e72 ** Changed in: mudlet Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1132260 Title: Perm triggers created after temp triggers run after temp triggers Status in Mudlet the MUD client: Fix Committed Bug description: Temp triggers normally run after perm triggers, however but not if the perm trigger was created later. For example, when you reinstall a package or a module, its perm triggers will be running after existing temp triggers. This creates an issue where perm triggers rely on the original MUD colors to do their work, which temp triggers later modify. If those perm triggers start running after temp triggers, they won't work. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1132260/+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
Re: [Mudlet-makers] [Bug 1117858] Re: Syntax errors inside setLink code can get shown on the wrong profile
that's clearly a bug. emit signalEchoMessage() is code from stone age :) logError() should be used everywhere Am 11.03.2013 01:09, schrieb Chris: It's because compileAndExcuteScript does this: emit signalEchoMessage( mHostID, QString( e.c_str() ) ); instead of doing logError. compileScript doesn't use logError as well, not sure if it should or not. https://github.com/Chris7/Mudlet2/commit/19b3266fa6b2ad3b3ad06bc5f63285498c2ce6f5 ** Changed in: mudlet Status: New = Fix Committed -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1117858 Title: Syntax errors inside setLink code can get shown on the wrong profile Status in Mudlet the MUD client: Fix Committed Bug description: Syntax errors inside setLink code can get shown on the wrong profile. For example, I had 2 tabs open, and was working with setLink in one of them. When setLink code had a syntax error in it, nothing showed up in the errors view - however on the main screen of another, completely unrelated profile, the error messages were showing up in white. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1117858/+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
Re: [Mudlet-makers] [Bug 1103873] Re: allow temp*Trigger to auto-remove itself after specified number of matches
this is on my personal feature list for 2.2 already Am 08.03.2013 04:32, schrieb Chris: I'd like to have a kill argument as well for triggers, which would auto- delete themself after matching -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1103873 Title: allow temp*Trigger to auto-remove itself after specified number of matches Status in Mudlet the MUD client: New Bug description: Currently to create tempTrigger and then remove it it is necessary to have global variable that stores its id. And then code of temp trigger must use that global variable to killTrigger itself. Please add parameter that will cause temp*Trigger to auto-remove itself after specified number of matches. Regards, Garagoth. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1103873/+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
Re: [Mudlet-makers] [Bug 1132260] Re: Perm triggers created after temp triggers run after temp triggers
1. tempTrigger types in general have an overall worse performance than regular triggers for various reasons - especially if they are the create to hit once and then kill type. 2. tempTrigs always run after regular mudlet objects (this has to be fixed in the package and module manager) because you have no control over matching order which you do for regular trigs so this is a necessity 3. I'm currently writing a technical reference manual that has all the necessary technical details behind Mudlet. Going to send you a copy to add to the mapper chapter and write a chapter on your module mananger. Am 08.03.2013 04:26, schrieb Chris: Are we adopting the notion in general that temporary triggers are 2nd class citizens to perm? I'm fine if so, just want to be clear since this doesn't actually strike me as a bug as much as a this is how we'd like things to work. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1132260 Title: Perm triggers created after temp triggers run after temp triggers Status in Mudlet the MUD client: Confirmed Bug description: Temp triggers normally run after perm triggers, however but not if the perm trigger was created later. For example, when you reinstall a package or a module, its perm triggers will be running after existing temp triggers. This creates an issue where perm triggers rely on the original MUD colors to do their work, which temp triggers later modify. If those perm triggers start running after temp triggers, they won't work. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1132260/+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
Re: [Mudlet-makers] [Bug 1124802] Re: Rooms are not properly removed on map load
I think it's best to have a clean wipe. #1 priority for the map loader is to always fail if the map version is newer than the current version of mudlet can cope with. I forgot to add this and it caused a ton of crashes in a game where 1 guy maps for everybody on the most recent version of Mudlet and not everybody has the most recent version of Mudlet. This leads to instant map corruption. Am 08.03.2013 04:24, schrieb Chris: Looking at this now. I'm wondering if we should keep a copy of the old map and reload that if the restore goes to hell. The downside is we'll be slowing down the load more by making a deep copy of the map. One alternative is to just wipe the current map for loading in, and if it fails the user just has to select a good map to load in. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1124802 Title: Rooms are not properly removed on map load Status in Mudlet the MUD client: Confirmed Bug description: When you load a new map in, current rooms are not properly removed first. This leads to an issue where if a room was deleted in a new map and you load it, it will not get painted, but it will exist - and show up in searchRoom, and roomExists will say it still exists. For a short demo, import the map with non-deleted room.dat map, and then import the map with deleted room.dat map in that order. You'll see that room 4855 was deleted, however it still shows up in searchRooms (causing problems) and roomExists(4855) will say true for it. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1124802/+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
Re: [Mudlet-makers] [Bug 1117858] Re: Syntax errors inside setLink code can get shown on the wrong profile
I don't believe that this bug is valid anyways, unless I get some proof :) I don't remember the exact implementation, but we absolutely need to keep backward compatibility for all functions in the API. This is the #1 priority in Mudlet. Never break old scripts. The various convenience optional args are also a problem. Am 08.03.2013 04:09, schrieb Chris: Is there any reason setLink is doing the lua stack work in that funky way? -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1117858 Title: Syntax errors inside setLink code can get shown on the wrong profile Status in Mudlet the MUD client: New Bug description: Syntax errors inside setLink code can get shown on the wrong profile. For example, I had 2 tabs open, and was working with setLink in one of them. When setLink code had a syntax error in it, nothing showed up in the errors view - however on the main screen of another, completely unrelated profile, the error messages were showing up in white. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1117858/+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
Re: [Mudlet-makers] [Bug 1114588] Re: Custom exit lines should be possible to be added from scripts
custom lines already have a bunch of line styles to chose from. connect(a,b) won't do because custom lines are no room connections but one directional point lists. you'd need a addCustomLine( roomID, luaTablecontainingTheLinePoints) Am 08.03.2013 03:50, schrieb Chris: We could make a new linestyle for non-cardinal exits (or better yet, make a function, call it connectRooms(a,b) that draws a default line, and have optional arguments for different line styles (the ones Qt has available)). We could expand the existing room exit adding code to take this optional argument as well for future use. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1114588 Title: Custom exit lines should be possible to be added from scripts Status in Mudlet the MUD client: New Bug description: Please add possibility to add custom exit lines between two rooms using LUA scripts or possibility to connect rooms with special exits with visual lines on map. Currentlu GUI only version exists and even with that it is not possible to connect rooms, just draw a line that does move with rooms. Mudlet: 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1114588/+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
Re: [Mudlet-makers] [Bug 1097543] Re: setExitWeight() works on non-existent exits
This would ensue a performance hit and is unnecessary imho. Am 08.03.2013 03:47, schrieb Chris: Is there a deleterious effect to this? -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1097543 Title: setExitWeight() works on non-existent exits Status in Mudlet the MUD client: New Bug description: setExitWeight() works on non-existent exits and remembers them - perhaps it shouldn't? To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1097543/+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
Re: [Mudlet-makers] [Bug 1142481] [NEW] Mouse click logic fix
info: custom line points editing relies on click+hold+move as you need to move tons of points usually other behaviour would be cumbersome imho Am 03.03.2013 18:16, schrieb Chris: Public bug reported: The logic (to me) in the mouse click handler is off. Events are triggered on the mouse press and not the mouse release. This results in things that are toggles (like clicking labels) being toggled when the user really wants to do things like move a label. In the recent label fix I released this is becoming an issue that I think needs to be tackled. To move a label you can't click then click-hold and move the label, you need to do it in 1 motion or else the label becomes un- selected. ** Affects: mudlet Importance: High Status: New -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1142481 Title: Mouse click logic fix Status in Mudlet the MUD client: New Bug description: The logic (to me) in the mouse click handler is off. Events are triggered on the mouse press and not the mouse release. This results in things that are toggles (like clicking labels) being toggled when the user really wants to do things like move a label. In the recent label fix I released this is becoming an issue that I think needs to be tackled. To move a label you can't click then click-hold and move the label, you need to do it in 1 motion or else the label becomes un- selected. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1142481/+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
Re: [Mudlet-makers] [Bug 1112223] Re: Package Exporter - Applies the /MudletPackage too early in the XML
Chris, you need to fix your git config to ignore whitespaces and you need to convert tabs to spaces in your editor. It's impossible to see what's changed in your commit right now - and this is a dangerous commit Am 03.03.2013 20:22, schrieb Chris: I think this fix solves it: https://github.com/Chris7/Mudlet2/commit/98681703771492e5cf3534978e1baacfd3d4ca52 Can someone else test? It passed my export/import tests, would be good for it to pass on another system. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1112223 Title: Package Exporter - Applies the /MudletPackage too early in the XML Status in Mudlet the MUD client: In Progress Bug description: I created two seperate XMLs for small systems. Both inserted the /MudletPackage tag just after the Trigger package ended. When attempting to import those XMLs, mudlet never read and imported the Alias' or Scripts. Mudlet ver. 2.1 - Current Build OS X Mountain Lion To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1112223/+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
Re: [Mudlet-makers] [Bug 1097953] Re: mudlet won't allow me to paste text being copied from an outside program
Please do the following to clarify the issue: left click on the command line, then right click and use the paste action from the popup menu to paste text. What happens? Am 27.02.2013 02:17, schrieb Sean Stone: Alright, so I installed 2.1 and it's still not allowing me to paste into mudlet from other programs. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1097953 Title: mudlet won't allow me to paste text being copied from an outside program Status in Mudlet the MUD client: New Bug description: So here's my problem: if I am in mudlet (using version 2.1) and on Windows 7 x64, I can copy and paste text just fine, both pasting to mudlet and to outside programs, however when I copy text, for example a URL in google chrome, and try to paste it into mudlet, it acts as if nothing is copied. However, if I then go to notepad and paste, it will paste just fine. I know a few others who have the same issue...I'd really like to see this getting fixed, it's greatly hindering my ability to do my job on Aetolia. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1097953/+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
Re: [Mudlet-makers] [Bug 1099688] Re: does not resolve the \t character
Then show me the RFC that defines it :-) Am 26.02.2013 17:20, schrieb Jeremy Akers: The behavior of tabs are well known and defined since the age of typewriters. Saying a tab character is technically undefined is absolutely incorrect. See: http://en.wikipedia.org/wiki/Tab_key and http://en.wikipedia.org/wiki/Tab_stop Yes most systems allow users to change the tab stop setting, but it generally defaults to 8 unless the user changes it. Just replacing tabs with x number of spaces is also wrong. Tabs are meant to create tabular data. They are generally set up to create 8 column tab stops So: Text\tMore text would display as: TextMore Text and: Someone\tMore Text Would be: Someone More text Basically the word More should always start at the 9th column due to the use of the tab character here. Even the crappy Windows telnet.exe handles tabs properly. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1099688 Title: does not resolve the \t character Status in Mudlet the MUD client: New Bug description: Mudlet does not seem to support the \t character (tab). On muds where this is used, Mudlet prints nothing. It does not indent at all. What is expected is either showing the tab character or 8 spaces, but neither happens, and things that are aligned using tabs make things look all wonky, like maps, etc. Mudlet: 2.1 OS: OSX 10.8.2 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1099688/+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
