Arbuckle
2009-05-22, 00:54
Hi all,
When I browse through my movie library and select movie info, cast information can be queried. When selecting an actor (say Hugh Laurie from Blackadder), I can select his name to browse the other movies / series in which he appeared. However, when selecting another movie (Sense and Sensibility) and clicking 'OK', only the title of the window (containing the movie title "Sense and Sensibility") and the plot information (autoscrolling in the large text area at the bottom of the movie information window) get updated. All other fields (director, writer, studio, genre, etc.) still contain information from "Blackadder", while you would expect information from Sense and Sensibiltiy to appear there.
Although I think this bug isn't platform specific, here is some platform information:
architecture: x86_64
distribution: Ubuntu
install method: .debs from PPA
kernel: 2.6.28-11-generic
svn revision: 19954 (9.04)
The debuglog doesn't contain any relevant information, I think this is just caused by some false logic somewhere in the XBMC core...
When I browse through my movie library and select movie info, cast information can be queried. When selecting an actor (say Hugh Laurie from Blackadder), I can select his name to browse the other movies / series in which he appeared. However, when selecting another movie (Sense and Sensibility) and clicking 'OK', only the title of the window (containing the movie title "Sense and Sensibility") and the plot information (autoscrolling in the large text area at the bottom of the movie information window) get updated. All other fields (director, writer, studio, genre, etc.) still contain information from "Blackadder", while you would expect information from Sense and Sensibiltiy to appear there.
Although I think this bug isn't platform specific, here is some platform information:
architecture: x86_64
distribution: Ubuntu
install method: .debs from PPA
kernel: 2.6.28-11-generic
svn revision: 19954 (9.04)
The debuglog doesn't contain any relevant information, I think this is just caused by some false logic somewhere in the XBMC core...