[quote="MarineBrat"]I'd like to see the addition of autocomplete for fields where a semicolon is already delineating a multiple entry.

For instance, if I'm editing the genre of a song and I type the letter "R", MediaMonkey automatically enters "R[color=#FF0000]&B[/color]" with the "&B part highlighted. If I continue typing the letter "o" I now have Ro[color=#FF0000]aring 20s[/color]. And continuing to type the letter "c" I now have "Roc[color=#FF0000]k[/color]".

But none of that works in a multiple genre context. If I have a song that's already listed as "Rock" and I want to add "Blues, using a semicolon to delineate them, the autocomplete functionality no longer works. This is true with many other fields besides just the genre.

I'm guessing that it would be a feat of programmatical genius to do it, based on the fact that you just don't see it, but it would be a nice feature.[/quote]

I really, really would love to see this, also! Is it at least feasible?

Definite agreement to your post.

If we could know where the bugs stand, we might be more productive in finding improvements rather than worrying over our favorite bug.

[quote="Seeker"]...(it's in here somewhere).... I'd stop bringing it up if I knew it was on a list somewhere with plans to fix it.[/quote]

Yep, I'm sure most of us have 1-2 bug/wishlist posts floating around the forums somewhere without "official" acknowledgement.
Although I hate the idea of bumping posts (annoying the developers and forum users) an alternative option for structured feedback is non existent.

Recently I had some interaction with Sqliteman and although its [url=http://sqliteman.com/bugtracker/view_all_bug_page.php]bug tracker[/url] looks a little amateurish it made me feel all warm inside :P

It is similar to the MM support ticket system but you can see all/selective "tickets" rather than just your individual "tickets"
At a minimum it might be possible for the developers to enter their own tickets (to do lists) then extract them to a forum post

[EDIT] I found 31 posts, a mixture of bug reports and wishes, where I started the thread.
That doesn't include any other posts I have added my support to.
I would really like to see a beta cycle dedicated to the cleaning up of all these outstanding issues, even if it is just to acknowledge:
1. Officially slated for version ...
2. Not in the direction we see MM being developed.
3. Core MM code is not suited for the change (significant rewrite)
4. Coding complexity outways user benefits/inconvience. (Maybe, if we can include it as part of another change)
5. Existing/possible script workaround
6. Included as part of XXX change, officially slated for version ...
7. We would rather work on exciting projects like XXX than boring YYY :P
8. etc etc

I would like to see if there is a "known bug list" with a "what do we plan to do" attached.

My "favorite" :) bug is the fact that Mediamonkey doesn't change the case on higher level folders (it's in here somewhere) during auto-organize. I'd stop bringing it up if I knew it was on a list somewhere with plans to fix it.

I'd like to see the addition of autocomplete for fields where a semicolon is already delineating a multiple entry.

For instance, if I'm editing the genre of a song and I type the letter "R", MediaMonkey automatically enters "R[color=#FF0000]&B[/color]" with the "&B part highlighted. If I continue typing the letter "o" I now have Ro[color=#FF0000]aring 20s[/color]. And continuing to type the letter "c" I now have "Roc[color=#FF0000]k[/color]".

But none of that works in a multiple genre context. If I have a song that's already listed as "Rock" and I want to add "Blues, using a semicolon to delineate them, the autocomplete functionality no longer works. This is true with many other fields besides just the genre.

I'm guessing that it would be a feat of programmatical genius to do it, based on the fact that you just don't see it, but it would be a nice feature.

I presume the devlopers have some idea about what they are hoping to accomplish with MM v3.0.4

The possibility to add custom icons into each individual skin!
Multiple Artists, ';' separator, etc. - discussion?
Improved Scripting Functionality?
Know bug/wishlist fixes/changes/improvements?
Etc, Etc

I believe that these should be posted officially with links to existing threads, or created new (sticky) threads, for users to discuss and offer functional requirements.

Users will also be informed if their specific bug/wishlist fixes/changes/improvements will be addressed in the current cycle.