MediaMonkey forum

Eyal wrote:I think it would be good to have some info about the length of the log file(s) in the Event Viewer.

how about an option to limit the file length, or maybe a button on the Viewer to split the log file and create a fresh empty new one.

Thanks for comments and suggestions. Those are very good, but I don't know where to put them and to keep compact window. If I put one new button or status bar, it would reduce useful area for the table which could be very problematic for someone who have small screen resolution and/or opened to many dockable panels. Showing information in the title bar is not practical because someone could choose to hide the title bar.

An information about number of rows could be displayed in the table header after the text "Track", for example "Track 865-965 in c:\...\EventLogger.csv". I know it is more correctly to put that information in the Event column (some event don't have information about track, e.g. OnStartup), but the Track column is much wider and could show such text without displaying too much empty space inside of Event column.

Also, I could add an option to limit the file length to the Options dialog...

Thanks for considering ZvezdanD, but I have no issue with space since I use it undocked, as I do with other scripts like Playlist Sandbox.

Eyal

Zvezdan:

Is there any way to have EL remember whether it was open or closed when restarting MM?

Nyn

nynaevelan wrote:Is there any way to have EL remember whether it was open or closed when restarting MM?

Event Viewer remembers if it was open or close - that state is stored with the ShowEventViewer key of the EventLogger section in the MediaMonkey.ini file. Do you want to say that it is not working for you?

No it's not but let me make sure I do not have any errant mediamonkey.exe's running, maybe that is what is causing it to not save...

Nyn

EDIT: I just checked, double checked and tripled checked and EL is always open when I restart MM, although I have it closed when I shutdown MM.

There is a new update: v2.1 - 2009-03-04
- Added: possibility to open a new log file when the file size is greater then specified value;
- Added: option in the context menu to open a specified log file into the Event Viewer;
- Added: display of information about opened log file and events range;
- Added: song position for Pause and Seek events;
- Improved: Event Viewer's skin automatically updated after skin change in the Options dialog box (only for supported skins).

There is a new update: v2.2 - 2009-05-13
- Added: OnPlaybackEnd event;
- Improved: skin styles;
- Fixed: error with Maximal log file size.

What is this script good for?

Sorry if I seem thick - and I don't mean to criticise the script in any shape of form, particularly since judging by the number of replies to this thread there is a real interest - but I don't understand why I would want to log every action I take in MM.

Could somebody enlighten me by giving some examples of suggested use? Many thanks!

Simply, Realtime Event tracker is essential tool for any script developer and tester when searching for bugs and ways ti improve your work.

Thanks for the reply, Peke - I didn't think of that! Yes of course, that would make a lot of sense...

As a user I like to keep track of my plays as well as when I start/shutdown MM. Especially when I am beta testing because it gives me an idea when I am getting AVs when shutting down MM.

Z:

I keep getting the following error for songs with a single quote in their name at their start and stop, but it doesn't state what script is causing the error, is there any setting I can select in EL that will let me know which script is generating this error?? At first I thought it was the Song Information Panel since that is the only new one, but I kept getting the error after I uninstalled the script so that can't be the cause.



EDIT: Never mind I figured it out, why is it my brain starts working after I've posted asking for help? Anyway it is the Monkey Rok script which is causing it.

Nyn

Thanks for the script. I am running it full time now as a light-weight debug mode.

Use of this script was critical in tracking down cause of an intermittent problem with MM and interaction with another script.

nynaevelan wrote:Is there any way to have EL remember whether it was open or closed when restarting MM?

There was a bug when you close Event Viewer on the [x] button from its Titlebar. However, the add-on remembered visible state if you closed it using its option from the View menu.

Anyway, there is the new update, v2.3 - 2011-06-22:
* Added: OnTrackSkipped and OnCompletePlaybackEnd events [MM4];
* Fixed: skin styles path [MM4];
* Fixed: visible state of Event Viewer after restart when it is closed on the [x] button from the Titlebar.

There is the new update, v2.4 - 2012-02-04:
* Added: view of events without writing to the log file: OnChangedSelection, OnTrackListFilling, OnTrackListFilled, OnNowPlayingSelectionChanged, OnNowPlayingModified, OnTrackListSelectionChanged and OnTrackListModified [MMx];
* Added: possibility for script developers to use Event Viewer and Logger for displaying/logging messages from their code (please read the Usage section).