Reply to thread

Message

Well, I finally got there. It was your hint about actor info that led me to the solution.

I think there is a little confusion with terminology as well that can lead to confusion. In the GUI, the settings refer to actor 'details' and in the column heading in the configuration app it says actor details:

[ATTACH=full]209449[/ATTACH]

In the database this information is held in a table called 'actorinfo' and other screen objects refer to this as actor info, which is really the same as actor details.

When you want actor details, the grabber and MP apps have to do a lot more work, which I mistook for being caused by looking for all actors in a movie when it was actually getting actor details/info. When the grabber doesn't do all of the iterations (the extra work), the actor info table gets very little information. It may be worth looking at why it needs so much extra work to get the full actor info because I suspect there is a way to get that data without all of the extra processing.

In the meantime, I'll change the wording on the screen (configuration) to make it clear that it is actor details that will be optional.

Thanks for helping me to finally get this sorted out.

<blockquote data-quote="Anthony Vaughan" data-source="post: 1286981" data-attributes="member: 153283">Well, I finally got there. It was your hint about actor info that led me to the solution.I think there is a little confusion with terminology as well that can lead to confusion. In the GUI, the settings refer to actor 'details' and in the column heading in the configuration app it says actor details:[ATTACH=full]209449[/ATTACH]In the database this information is held in a table called 'actorinfo' and other screen objects refer to this as actor info, which is really the same as actor details.When you want actor details, the grabber and MP apps have to do a lot more work, which I mistook for being caused by looking for all actors in a movie when it was actually getting actor details/info. When the grabber doesn't do all of the iterations (the extra work), the actor info table gets very little information. It may be worth looking at why it needs so much extra work to get the full actor info because I suspect there is a way to get that data without all of the extra processing.In the meantime, I'll change the wording on the screen (configuration) to make it clear that it is actor details that will be optional.Thanks for helping me to finally get this sorted out.</blockquote>

[QUOTE="Anthony Vaughan, post: 1286981, member: 153283"] Well, I finally got there. It was your hint about actor info that led me to the solution. I think there is a little confusion with terminology as well that can lead to confusion. In the GUI, the settings refer to actor 'details' and in the column heading in the configuration app it says actor details: [ATTACH type="full"]209449[/ATTACH] In the database this information is held in a table called 'actorinfo' and other screen objects refer to this as actor info, which is really the same as actor details. When you want actor details, the grabber and MP apps have to do a lot more work, which I mistook for being caused by looking for all actors in a movie when it was actually getting actor details/info. When the grabber doesn't do all of the iterations (the extra work), the actor info table gets very little information. It may be worth looking at why it needs so much extra work to get the full actor info because I suspect there is a way to get that data without all of the extra processing. In the meantime, I'll change the wording on the screen (configuration) to make it clear that it is actor details that will be optional. Thanks for helping me to finally get this sorted out. [/QUOTE]