

Also, they're easily customisable, and the bar is dynamically created from a list: The colours on the horizontal lists (the info bar) are roughly chosen. At the moment all I've managed to do is give the channel tabs an unwanted backgroundĢ. I need to read up a bit more on CSS but once I do there will be a single border around it. I've borked up the border on the chat window. Made some changes as the narrow chat window was frustrating me and I really wanted to see if the horizontal lists would work well or not.Ĭheck it out, let me know what you think.ġ. Reading that message this morning gave me loads of motivation to complete both of these projects Good news with the aff tracking system in the other thread - Elyni has offered to plug it into Entropy, which means we'll have people from that system testing it as well. They are completely self-sufficient triggers, no associated scripts) But if you prefer being spammed by the standard formatting, it's as simple as disabling the triggers. At least with Fortress they show up as normal text from the mud so they're easy to fix. (wtf is with systems with spamming the user out with info echoes? Citadel/Fortress is one of the worst, but every single system I have ever seen, with the single exception of IMTS, does this to some degree. Type messages and replacing them with (stuff) (in) (brackets) In the screenshot, you'll see that I've done a significant amount of work in gagging the: At this early stage it will be a simple list, all in white. It's got a relatively small miniconsole dedicated to it.īox2 above it is for enemy affs. It will go where boxes 6 and 7 are, which will be combined into a single box 7. All of the modeal buttons work - except for reset. I set the buttons to sienna just to make sure the default white borders can actually be as easily rewritten as I claimed they would be. Are there any other GUI components that people feel really should be in every GUI, and not left up to individuals to add on their own? How about a display of defenses missing? (This one is particularly difficult to get data for if you use Fortress to manage your defs)ģ. Should I include a display of afflictions on self?Ģ. By default, it'll all be boring white borders.ġ.
#Chatmonitor 3k mudlet skin
The stylesheets are all done with CSSMAN, which means people can skin the look as they please. An option to create top and/or bottom bar spaces (basically, these are already created, but I'll comment out those sections as not everyone likes such complex GUIs.Ħ. An option to compress the chan cap and map display to use one third of the vertical space each, rather than one half, freeing up the third third for personal additions.ĥ. This will be customisable - there is a table with the details of most system toggles/commands that make sense to be here, and another table where you list which ones you want to actually be created as GUI objects (and in which order).Ĥ. buttons/toggles down the left side for controlling Fortress system stuff. The GUI will be quite simple, but created in such a way that individual customisation/additions is easily done.ġ. I don't get a huge amount of time to spend on these projects, but I will put the effort in to complete the GUI and put it here to share. Another option is to post-process already recorded files (.vfw).I have a partially-finished Mudlet GUI for Fortress. You can evaluate each event and create a chatter report.
#Chatmonitor 3k mudlet software
It then evaluates the recording to determine if a chatter event has occurred.Īfter evaluation, the software will display any detected events. The software uses the RecorderVIEW package to record the test’s inputs. The VibrationVIEW Chatter Monitor software package detects contact chatter events.

You can then evaluate the results to determine the contacts’ effectiveness. Any change in the contacts’ voltage will indicate a chatter event. Re-create chatter events in a laboratory setting by mounting the relay or contactor in the recommended position, simulating a shock test or earthquake, and monitoring the test. Otherwise, a contact chatter event can occur, leading to disconnection, wear, or damage. When a relay is subjected to a large shock event, such as an earthquake, the electromagnetic coil holding the contacts in the energized position and the spring tension holding the contacts in the de-energized position must be strong enough to withstand the force of the event. It is detected in the mechanical relay or contactor of the device under test. Chatter is an event that can occur in response to shock vibration.
