Reply to thread

Message: <blockquote data-quote="fforde" data-source="post: 358801" data-attributes="member: 52082">Hi Ronner, thanks for all the feedback (and thanks for giving it in a constructive way <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue    :p" loading="lazy" data-shortname=":p" /> ). Marvenius is right most of this is either a known bug or on the schedule. I will go through and point you to the scheduled issues for each suggestion though. Before I begin though, please remember that Moving Pictures has only been available for 4 months, so it is a pretty young plug-in. We are making steady progress but there are only two really active developers on the project so it all takes time.Well everything else works fine most likely because none of them do realtime updates linked to file system changes. Moving Pictures is very active in maintaining your collection based on things being added and deleted from your watch folders, so when you have two copies of Moving Pictures attached to the same database, you get some conflicts.Multi-seat support is asked for a lot though so we will definately implement it. Currently our plan is to do things in two phases. <a href="http://code.google.com/p/moving-pictures/issues/detail?id=223" target="_blank">Phase one</a> simply involves an option to turn off the movie importer for client systems. Meaning that the main system is the only one that would be automatically importing movies and artwork. There are still some problems with this, for example the client systems wont know when movies have been added or updated, so at best they would just have to periodically reload everything from the database. Obviously not ideal. The idea though is this enhancement would create a workable situation for the time being while the larger phase two enhancement is shceduled/worked on.<a href="http://code.google.com/p/moving-pictures/issues/detail?id=23" target="_blank">Phase two</a> is a proper multi-seat setup with the main instance working as a proper server and the satellite  installs, proper clients. So there would be no centralized database, the different versions of Moving Pictures would just talk to each other across the network. This is a more complicated solution but solves a lot of the problems I mentioned above.<a href="http://code.google.com/p/moving-pictures/issues/detail?id=98" target="_blank">This is scheduled</a> for a future version, although it is a fairly easy fix so we may pull this forward a bit. We are doing a lot of changes to the config screen right now so it may be a good idea to go ahead and knock it out...Based on your suggestion above I am assuming all of your import paths are on network drives? If this is true you are probably experiencing <a href="http://code.google.com/p/moving-pictures/issues/detail?id=245" target="_blank">this bug</a>. The text in that issue is not so descriptive, but basically, in 0.6 sometimes the Windows service that watches the file system for changes crashes when connected to a network drive. This has already been resolved for 0.7.As for prompting the user for matches that are not auto-approved, <a href="http://code.google.com/p/moving-pictures/issues/detail?id=83" target="_blank">this too is scheduled</a>.I feel like our matching process is excellent so I am kind of surprised to hear you say this. You gave a bad example though, as you mentioned "Guns is a TV Show, and as you know Moving Pictures is intended for movies. The IMDb script actually uses regex to filter out TV Shows from the search result to achieve better auto-approval rates. This is a design decision, we have intentionally chosen to have a narrow focus on Movie content to create a more specialized experience. See <a href="https://forum.team-mediaportal.com/moving-pictures-284/tv-show-support-music-dvds-45417/" target="_blank">here</a> for more details.A tip though, in the manual search dialog, if you are using the IMDb script, if you type in the IMDb ID instead of the title, it will match to the TV Series anyway.<a href="http://code.google.com/p/moving-pictures/issues/detail?id=212" target="_blank">This of course is planned.</a>Well the idea is to keep things uncluttered. If we put every menu item on the context menu of every location of the GUI, there wouldn't be much point in calling it a "context menu" would there? And more importantly, it would not be very usable with a dozen different unrelated options packed into one menu.Besides if you want to change the watched status of a large number of movies at once, which is what I get t he impression you are trying to do, you are much better off doing it from the GUI, as you can select multiple movies at once and make a bulk change.Again, <a href="http://code.google.com/p/moving-pictures/issues/detail?id=17" target="_blank">planned</a>. Most of the information you are describing is not readily available without integration of third party libraries though, so it is not as simple a task as it seems.Yeah this is a skin issue. Most skins have a semi-transparent background that overlays the fan-art for this specific purpose though...Of course <a href="http://code.google.com/p/moving-pictures/issues/detail?id=38" target="_blank">this is planned too</a>.So thanks for the feedback, hopefully that gives you an idea of where we are at. I would suggest skimming the <a href="http://code.google.com/p/moving-pictures/issues/list" target="_blank">Issue List</a> though because it is actively updated and should give you a pretty good idea of our roadmap. If you have any ideas to contribute to anything I have linked above (or other issues for that matter) feel free to post in the appropriate issue.</blockquote>

Verification