On Mon, 23 Aug 2010, Francisco Eduardo Álvarez Solano wrote:
2010/8/21 Paul <strifek...@users.sourceforge.net>
That's odd, I can't replicate either of those functions - I'm
using 1.9.0 - I just get an empty directory if there's an fxd
command file in it and if I put the fxd location in the relevent
menu items nothing shows up in Freevo. I'm using bash scripts to
launch all of the applications but see you have successfully
used with picasa, any other tips of here to go from here?
I'm using Ubuntu 10.04 and Freevo 1.8.2 with this setup.
I've tried Freevo 1.9.0 and, yes, I can't see the new menu entries. I think
it's related to the plugin 'command.fxdhandler'. When I've enabled it in
1.9.0 in local_conf.py, I've got an error whenever I try one of the menus
that have a fxd file:
plugin.activate('command.fxdhandler')
$ freevo
Traceback (most recent call last):
File "/datos/freevo190/lib/python2.6/site-packages/freevo/fxditem.py",
line 132, in parse
parser.parse()
<snip>
self.spawnwm = config.COMMAND_SPAWN_WM
AttributeError: 'module' object has no attribute 'COMMAND_SPAWN_WM'
Looks like you need to add 2 new variables in your local_conf.py called
COMMAND_SPAWN_WM and COMMAND_KILL_WM
ie.
COMMAND_SPAWN_WM = ''
COMMAND_KILL_WM = ''
These appear to be used to start and stop a window manager using the
<sqawnwm> tag. You probably don't need this but defining these should
allow you to use the plugin.
What is odd is that the plugin should defined these automatically?! Looks
like another bug to bash.
Cheers
Adam
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
