It's cool like that yes I didn't mean thumb, extra fanart FTW. My question was more like if it's tied to
<fanart></fanart>
or
<fanartpath></fanartpath>
fr500 Wrote:It's cool like that yes I didn't mean thumb, extra fanart FTW. My question was more like if it's tied to
<fanart></fanart>
or
<fanartpath></fanartpath>
Actually, for launchers the extra fanart path is equal to the
<fanartpath></fanartpath> tag. For roms the extra fanart path is linked to the
<fanart></fanart> tag (same path but without the filename).
Honestly I did not know what will be the best tag to use to link the extra fanarts (what why I have indicated that I need skinners feedback into the change log).
<fanartpath></fanartpath> seems to be the first option that come in mind. But if you decide to change and use fanarts images that are not into this default directory... did the extra fanarts path will still linked to
<fanartpath></fanartpath> or will be updated with the new
<fanart></fanart> value? Any idea what will be the best ?
srsobieraj Wrote:I'm not sure I understand. Do you want to edit individually or do you want to use a scraper?
Scraping can be done in 2 ways: Automatic and semi-automatic.
Automatic runs the scraper and assigns info to the ROM based on the best match.
Semi-Auto runs the scraper but asks the user to make the best match. There is presently no way to select "No match" in this mode.
If "Off" is selected, ALA will import the ROMs but not gather any info. You can then go and scrape each ROM individually.
If you're talking about the "Import plot from file" option, then you have to set each plot manually at the moment. ALA doesn't look to see if you have a plot file already (mostly because there is no pre-defined location for plot files). Perhaps this could be added in future versions, by specifying a Plot path the same way we set Thumbnail and Fanart paths.
1. Couldn`t find this on the Wiki
Thanks for all the changes so far
ps. my thumbs and fanarts still give error,
thumbs/fanart
Also there is the option "import during scan" How do you start the scan ? for none/auto/semi-auto
Also how does one install the advanced.launcher.console.icons.pack.zip ? Also 1.
edit: Tried v1.0.4 and still almost same error
thumbs/fanart
While scraping the fanart/thumb, it brings up the image, I select, then in the fanart/thumb folder
it then creates a file game* (no extension), an empty file named after the game,
and obviously fails to download while displaying " error Script failed! :addon.py"
timdog82001 Wrote:I recently updated advanced launcher and deleted and redid all my emulator entries in order to scan in the artwork....but some of the emulators that previously worked with the default arguments provided by advanced launcher froma previous version now no longer work with the arguments provided from the newest version of ALA.
I don't recall what if any default arguments were previously associated with MameUI32, but right now its just "%rom%" and this launches mame alright, but mame throws up "ERROR: required files are missing, the game cannot be run." I assure you, the files are most certainly there.
Anyway, what arguments are you guys using on Windows for MameUI and snes9x? It was working fine for me yesterday before I redid all the advanced launcher entries. I found a list of mameui arguments, but none of them seemed relevant. snes9x also is no longer working. It opens up the snes9x window but nothing happens, its just black inside the window.
I finally found in MameUI the "Directory" Section for the roms. MAMEUI, found the game and could play but it couldnĀ“t start with advanced launcher because of a different Filename, check this if you got this problem.
Angelscry Wrote:Actually, for launchers the extra fanart path is equal to the <fanartpath></fanartpath> tag. For roms the extra fanart path is linked to the <fanart></fanart> tag (same path but without the filename).
Honestly I did not know what will be the best tag to use to link the extra fanarts (what why I have indicated that I need skinners feedback into the change log).
<fanartpath></fanartpath> seems to be the first option that come in mind. But if you decide to change and use fanarts images that are not into this default directory... did the extra fanarts path will still linked to <fanartpath></fanartpath> or will be updated with the new <fanart></fanart> value? Any idea what will be the best ?
I'd say fanartpath but guess the other skinners should post their opinions on this issue too
KiSUAN Wrote:Spanish Translation Update Spanish String.xml
Thank you. It will be added in the next version.
fr500 Wrote:I'd say fanartpath but guess the other skinners should post their opinions on this issue too
I think that using the
fanart tag of an item to define the extrafanart path is less restrictive than using the
fanartpath tag of the launcher.
If all your fanarts images are into the fanartpath it will be exactly the same.
But if your fanarts images are into different directories, your extrafanarts images will also have to possibility to be into different directories and not defined by the fanartpath of the launcher.
Angelscry Wrote:I think that using the fanart tag of an item to define the extrafanart path is less restrictive than using the fanartpath tag of the launcher.
If all your fanarts images are into the fanartpath it will be exactly the same.
But if your fanarts images are into different directories, your extrafanarts images will also have to possibility to be into different directories and not defined by the fanartpath of the launcher.
I must ask because I feel I'm missing something, how you get the path for fanart?
Because the only thing I can fetch is the complete "path + image name" with Listitem.Property(Fanart_Image). Listitem.Path gives me the plugin path. So I feel something is missing/wrong here.
KiSUAN Wrote:Listitem.Path gives me the plugin path. So I feel something is missing/wrong here.
Ok... I have just checked. Seems that for programs the Listitem.Path gives always the plugin path. What ever I assign, the returned value by XBMC is always the plugin path.
Ok... I think I understand the problem. When using XBMC with movies the Listem.path is related to the path of the movie files. When using XBMC with music the Listem.path is related to the path of the audio files. For the same reasons, when using XBMC with programs the Listem.path is related to the path of the add-on files (and not to the path of the file focused by the add-on.). I think that's why the Listem.path return the add-on path. It makes sense. What I can do is to replace the
Listem.path by the
Listem.trailer for next version. It is not really consistent with the rest of the XBMC path and skin management... but I do not think I can do better actually.
Listitem.trailer is fine with me.
We've done an option to choose where all the game stuff can be customized by the user in Cirrus Extended. The code for fanart image and extrafanart is in myprograms.xml the trailer and thumbs are in the respective view file.