Hi,
if I am not mistaken, the problem is that the graphwidget plugin
compiles several filters when it is first executed, which fails, because
the compileFilter-function uses the performance framework which in turn
has not yet been initialized by startup.js.
So this seems to be a problem with the module execution order. However I
don't know if this is a bug and the Filter module has to assure that the
performance framework has been loaded or if this expected behaviour and
one is not supposed to use the Filter module in such a way.
Anyway, you should be able to get it to work by postposing the Filter
compilation in graphwidget.js until it is necessary.
Regards,
/Andreas
Am 31.05.2014 13:21, schrieb Danielo Rodríguez:
I removed the plugin from my wiki.
I looked into the code and this seems to be related to TW5 new core.
Since I'm not familiar on what new features could cause this I'm
afraid I will not be very useful here.
Sorry.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
