MediaMonkey forum

I just want to say that for someone who is not using MM for reproduction, those two File size columns (from Top # * and Top # Played *) would return significantly different values in same way as Track has different values than Played column and Length will have different values than Play Time. So, I think that those two File size columns should have different names as well, since somebody could take a look at them, to see different values and to think that something is wrong with the script. Because of that I suggested to add "(played)" to it.

nynaevelan wrote:I assume when you add the Option sheets you will include an option to suppress the tables for the values that do not have any tracks to meet the criteria?

There is a new update: v1.2 - 2009-04-12
- Added: Options Sheet and Options dialog with options for display of sections in the report.

ZvezdanD wrote:

nynaevelan wrote:I assume when you add the Option sheets you will include an option to suppress the tables for the values that do not have any tracks to meet the criteria?

There is a new update: v1.2 - 2009-04-12
- Added: Options Sheet and Options dialog with options for display of sections in the report.

Z:

My options are not taking an effect, even after I restart MM I still get all the same sections. Here are the options which I have selected:



Nyn

There is a new release with fixed bug. Before installation please uninstall old version, since location of the script is changed to the Auto folder.

Z:

I always get this error when selecting a particular filter from the drop down box. It works ok when it is the first filter run but when I try to select it after running a different filter, I get the error:



Nyn

Great update. I have one question, and one suggestion though. Now that you have implemented the ability to exclude certain parts, does this simply hide these sections, or does it also prevent the SQLs running that would fill these sections if selected? The suggestion is that since you've now got an options sheet, maybe "Top #" is an option that should be moved from the script itself, and into this new option sheet? Just seems it would make more sense to make such an important option more visible. Only a suggestion however, well, I guess I actually suggested it in the form of a question, haha. Alwell...

EDIT: Just remembered something that has bothered me about the original Stats script for a while now. The window has the option to Maximize, however if you do, it covers the entire screen. That includes the task bar, which isn't usual behavior for Windows. Any way to get it to only cover the "Application Area" (a.k.a., the entire screen, except where the Taskbar is) when Maximized? Maybe this is an MM bug, since I semi-recall Bex's SQLViewer doing the same. Hm...

That too could even be undesired, now that you've added a progress bar which shows on the Main MM window, which would be hidden behind an empty Stats window when Maximized, so... I don't know. *Shrugs*

Mizery_Made wrote:Now that you have implemented the ability to exclude certain parts, does this simply hide these sections, or does it also prevent the SQLs running that would fill these sections if selected?

Of course it also prevents calculating of SQL queries. Why should I slow down the script with something which is not displayed?

The suggestion is that since you've now got an options sheet, maybe "Top #" is an option that should be moved from the script itself, and into this new option sheet?

Sorry, but I don't understand what you are suggesting.

The window has the option to Maximize, however if you do, it covers the entire screen. That includes the task bar, which isn't usual behavior for Windows. Any way to get it to only cover the "Application Area" (a.k.a., the entire screen, except where the Taskbar is) when Maximized? Maybe this is an MM bug, since I semi-recall Bex's SQLViewer doing the same.

I already reported it: Dialog boxes should not overlap Task Bar - but nobody responded Maybe if I post it in the Beta forum...

nynaevelan wrote:I always get this error when selecting a particular filter from the drop down box.

What is a name of this filter?

On the db you have it is Editing - Library Editing but on mine I renamed it Primary - Library Editing. Let me know if you need an updated version of the db.

Nyn

nynaevelan wrote:On the db you have it is Editing - Library Editing but on mine I renamed it Primary - Library Editing.

There is a new revision. Thank you very much for the report.

ZvezdanD wrote:

nynaevelan wrote:On the db you have it is Editing - Library Editing but on mine I renamed it Primary - Library Editing.

There is a new revision. Thank you very much for the report.

You are VERY welcome, it is the least I can do for your fine work. I will let you know if I have any problems with the new version and I am looking forward to how you will incorporate MN into the script.

EDIT: All is well with the filters.

Nyn

I might have read that thread you posted and simply forgot. Anyway, it makes sense to not run the queries when they are disabled, so I was just curious if this is how you did it, or due to limitations, you have to just not display the information. As for the suggestion, inside the script there is a variable you can change which changes the number of artists/albums/etc listed in the Top # sections. It's default is 10, but you can set it to any number you want, such as 25 (which is what I use.) This seems like an important setting, and since you've now created an options sheet for the script, maybe it should be moved to the options instead of a setting within the script itself. Make more sense this time? Sorry if not.

Mizery_Made wrote:Make more sense this time?

I see now what you mean. Thanks for the suggestion, it will be implemented in the next version.

The script doesn't play too nicely when a Filter Name contains an apostrophe. Tried running it on a filter I have named "TI -- Albums With -- Only --Albums--'s" and it gave me an error, something about ": near s" or something, which seems to point to the apostrophe. I renamed the filter and removed it, and it ran fine. Seems it needs to be escaped or something in the SQL query or something.

Mizery_Made wrote:The script doesn't play too nicely when a Filter Name contains an apostrophe. Tried running it on a filter I have named "TI -- Albums With -- Only --Albums--'s" and it gave me an error, something about ": near s" or something, which seems to point to the apostrophe. I renamed the filter and removed it, and it ran fine. Seems it needs to be escaped or something in the SQL query or something.

Thanks for the report and earlier suggestions. I don't have Gold version, so I cannot check some new filter with the "'", but I suppose that I resolved the mentioned bug.
v1.3 - 2009-05-05
- Added: option to set the number of Top items;
- Fixed: error with filter names which contain "'".