Ok, so currently I have LibSharedMedia-2.0, LibSharedMedia-3.0, SharedMedia, SharedMedia-2.0, SharedMediaAdditionalBackgrounds, SharedMediaAdditionalFonts, SharedMediaAdditionalFonts-2.0 and finally SharedMediaLib all installed, all currently active. What should I dump, and what can I keep? Thanks.
As for the libraries (the ones with Lib in their name), keep those that your addons use. If you use embedded libraries (you just download your mod and all libs are inside) then they already come with these, and you can ditch the Libs.
Keep SharedMedia, ditch SharedMedia-2.0. SharedMedia has been updated to handle all libraries.
If you want the media that comes with SharedMediaAdditionalBackgrounds, SharedMediaAdditionalFonts, SharedMediaAdditionalFonts-2.0 then keep them - if you don't, then delete them. They're just additional packages.
SharedMedia has been updated to handle all libraries.
Uhm, I just installed SharedMedia because I wanted some additional textures in Omen2 besides the Blizzard ones. I get the textures, but at the same time BugSack reports 79 errors now...
[2008/04/05 22:10:54-136-x79]: Omen\Frame.lua:179: attempt to index field 'Anchor' (a nil value)
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...men\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher":4: in function <[string "safecall Dispatcher"]:4>
<in C code>: ?
<string>:"safecall Dispatcher":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
LibSharedMedia-3.0\LibSharedMedia-3.0.lua:153: in function `Register'
SharedMedia\Core.lua:36: in function <Interface\AddOns\SharedMedia\Core.lua:30>
That error isn't related to SharedMedia; it looks like Omen is doing something wrong. Try updating again and see if it's been fixed; if not, try downloading an older version of Omen from before you updated: http://files.wowace.com/Omen/
The culprit seems to be Chronometer, odd as that may sound. When I move the Chronometer folder out of the Addons one, the Omen error goes away. Put the Chronometer folder back, and the Omen error pops back up. Nothing else is changed, just moving the Chronometer folder.
I know Chronometer isn't maintained anymore. That's a shame, since I have tried several alternatives, but none do what Chronometer used to do so well. Oh well.