Global gSysMessage leaks messages between profiles
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mudlet |
Fix Released
|
Medium
|
Stephen Lyons |
Bug Description
Current Git code (at least) uses a global QStringList qSysMesssages to hold initialisation messages (both Ok and Error types) from the Lua subsystem (TLuaInterpreter) and from the Server connection process (cTelnet) unfortunately the code in cTelnet:
This means that upon starting up a second profile in a Mudlet instance messages from the first profile are shown.
Code that removes duplicate messages merely confuses the information displayed with the result that if a problem has been fixed between the first and second profiles being started it is possible to get an "Error" message from the first and then an "Ok" for the same module from the second.
I have coded a fix at my branch mudletDev_
As a highly contrived example I un-installed all the external non-Mudlet Lua modules that Mudlet uses and started up the Mudlet instance, I fired up one profile, then loading in just my distribution's lua-filesystem package, and then started a second profile before taking a composite screen shot (it took more than one screen to show all the text!) that is attached here. This is the output from the current mudletDev branch code.
Changed in mudlet: | |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in mudlet: | |
status: | In Progress → Fix Committed |
Changed in mudlet: | |
status: | Fix Committed → Fix Released |
Blast, got my branches confused I MEANT TO SAY my mudletDev_ fixGSysMessage branch at https:/ /github. com/SlySven/ Mudlet2/ tree/mudletDev_ fixGSysMessage. And this is the same output from it.