Mudlet-2.0 release candidates [latest: Mudlet 2.0 final]
Re: 2.0 snapshots
I did get a crash while using the 'copy to HTML' feature - I think it's because some text came in while I was copying. Will get a backtrace next time.
Re: new features/functions in 1.2.0-pre8
I just had perhaps 29 minutes of a 30 minute log not get saved to the log file.Omni wrote:After finally remembering to start the logger, I logged a long Free-For-All in Lusternia. Once it finally ended I stopped logging and when I went to check the log I got this. A full 9 minutes of the log gone. You can see that it skips a large chunk at the end by the timestamps.
I don't know how to help track this down.
I have save to html checked.
Re: 2.0 snapshots
I also got that, first time I tried to use it. I was in a rush to leave so I didn't pay attention to what was happening at the time, but I DID copy a fair bit - maybe 10 screens worth - by holding down the left mouse button and scrolling with the scroll wheel.Vadi wrote:I did get a crash while using the 'copy to HTML' feature - I think it's because some text came in while I was copying. Will get a backtrace next time.
Re: 2.0 snapshots
Here it is:Vadi wrote:I did get a crash while using the 'copy to HTML' feature - I think it's because some text came in while I was copying. Will get a backtrace next time.
Program received signal SIGSEGV, Segmentation fault.
TBuffer::bufferToHtml (this=<value optimized out>, P1=<value optimized out>, P2=<value optimized out>) at TBuffer.cpp:3161
3161 if( needChange
(gdb) bt
#0 TBuffer::bufferToHtml (this=<value optimized out>, P1=<value optimized out>, P2=<value optimized out>) at TBuffer.cpp:3161
#1 0x0000000000573468 in TTextEdit::copySelectionToClipboardHTML (this=0x2cb5a30) at TTextEdit.cpp:1322
#2 0x000000000065681c in TTextEdit::qt_metacall (this=0x2cb5a30, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7fff22892dc0) at tmp/moc_TTextEdit.cpp:83
#3 0x00007f7097a6f0f8 in QMetaObject::activate (sender=0x264fe60, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0)
at /var/tmp/qt-src/src/corelib/kernel/qobject.cpp:3272
#4 0x00007f70982e3942 in QAction::triggered (this=0x6, _t1=false) at .moc/release-shared/moc_qaction.cpp:263
#5 0x00007f70982e4d40 in QAction::activate (this=0x264fe60, event=<value optimized out>) at /var/tmp/qt-src/src/gui/kernel/qaction.cpp:1256
#6 0x00007f7098786fa3 in QMenuPrivate::activateCausedStack (this=0x6b7a600, causedStack=..., action=0x264fe60, action_e=QAction::Trigger, self=true)
at /var/tmp/qt-src/src/gui/widgets/qmenu.cpp:993
#7 0x00007f709878cc12 in QMenuPrivate::activateAction (this=0x6b7a600, action=0x264fe60, action_e=QAction::Trigger, self=80) at /var/tmp/qt-src/src/gui/widgets/qmenu.cpp:1085
#8 0x00007f709834ac59 in QWidget::event (this=0x6a79a30, event=0x7fff22893910) at /var/tmp/qt-src/src/gui/kernel/qwidget.cpp:8187
#9 0x00007f709878c69b in QMenu::event (this=0x6a79a30, e=0x7fff22893910) at /var/tmp/qt-src/src/gui/widgets/qmenu.cpp:2410
Re: 2.0 snapshots
I have a quick, unrelated question about the 2.0 snapshot. Concerning the IRC client baked in, is there a way to change my name, instead of being known as Mudlet8675309? This could be an IRC-specific question (to which I know next to nothing about).
Re: 2.0 snapshots
Is a problem with one of the new functions (setRoomUserData/getRoomUserData)....
User data is not being saved yet.
The following is a simple test script. It works fine the first session it runs but fails after you close mudlet and reopen(tested on a profile without any other mapping)
User data is not being saved yet.
The following is a simple test script. It works fine the first session it runs but fails after you close mudlet and reopen(tested on a profile without any other mapping)
Oh... and it would be nice if 'getRoomUserData' returned nil if the key does not exist (currently there is no good way to trap an error with it)
Last edited by Omit on Sat Jan 29, 2011 12:45 am, edited 1 time in total.
Re: 2.0 snapshots
I'm using Mudlet-2.0-rc1-snapshot14012011.exe and I've noticed a rather significant bug.
Scripts that are supposed to be deactivated are still executing themselves upon being edited. It would appear that the method mudlet uses to find bugs in scripts is to simply try and execute them.
Deactivated scripts do not run on start-up, and are working as intended in that regard.
How to replicate an example: Create a new script, and have it do somthing simple, like echo("HI!"), deactivate it, and then click the save button. You should notice 'HI!' printed to the main window, even though the script is supposed to be deactivated.
Scripts that are supposed to be deactivated are still executing themselves upon being edited. It would appear that the method mudlet uses to find bugs in scripts is to simply try and execute them.
Deactivated scripts do not run on start-up, and are working as intended in that regard.
How to replicate an example: Create a new script, and have it do somthing simple, like echo("HI!"), deactivate it, and then click the save button. You should notice 'HI!' printed to the main window, even though the script is supposed to be deactivated.
Re: 2.0 snapshots
When a script is deactivated, it only means that it's event handlers won't be calling it. Functions declared inside it are still callable and the script is called & executed on save.
Re: 2.0 snapshots
I'm using the mac version, and have encountered a few bugs so far. I've attached a compilation of the ones I can capture.
From top to bottom:
Toolbar, the Help Chat button text gets cut off
In editing a trigger, the multiline drop down does not work - line delta can't be set. Also note on the right, the foreground and background highlight color boxes overlap
Spell checker is fairly buggy. I can't explain that one more than what you see.
Built-in IRC chat window can be maximized/restored, minimized, or closed. However, it can not be resized.
Bugs I can't screenshot:
When using a trackpad to scroll up, via multitouch, it will not scroll proper. This is unique to mudlet, so is not the trackpad -edit: When I use a scrollwheel on a real mouse, it works fine.
When I select text, and right click, I get a dialog box, "Copy/Copy as HTML". When I click either of these options, the text is correctly copied to the clipboard in the selected format. However, a second (slightly smaller) box pops up in the same position, with the same options. Clicking either of these options works as well correctly, and then the box disappears.
When trying to move a something out of a folder (IE: a trigger/alias/whatever), in the windows version you can drag it to the top (where it says Triggers/Aliases - Input Triggers/Scripts or whatever) and have it come out of the folder. This is not the case in the mac version, but would be infinitely helpful!
From top to bottom:
Toolbar, the Help Chat button text gets cut off
In editing a trigger, the multiline drop down does not work - line delta can't be set. Also note on the right, the foreground and background highlight color boxes overlap
Spell checker is fairly buggy. I can't explain that one more than what you see.
Built-in IRC chat window can be maximized/restored, minimized, or closed. However, it can not be resized.
Bugs I can't screenshot:
When using a trackpad to scroll up, via multitouch, it will not scroll proper. This is unique to mudlet, so is not the trackpad -edit: When I use a scrollwheel on a real mouse, it works fine.
When I select text, and right click, I get a dialog box, "Copy/Copy as HTML". When I click either of these options, the text is correctly copied to the clipboard in the selected format. However, a second (slightly smaller) box pops up in the same position, with the same options. Clicking either of these options works as well correctly, and then the box disappears.
When trying to move a something out of a folder (IE: a trigger/alias/whatever), in the windows version you can drag it to the top (where it says Triggers/Aliases - Input Triggers/Scripts or whatever) and have it come out of the folder. This is not the case in the mac version, but would be infinitely helpful!
- Attachments
-
- 4 bugs.
- mudletbugs.png (140.53 KiB) Viewed 8318 times
Re: 2.0 snapshots
In regards to the track pad I can confirm that it doesn't work. It also doesn't like to scroll the mapper, and makes zooming the 2D map impossible (because the sliders don't seem to work on it).