Hi,

On 18.10.2012 06:15, xyliu80@gmail.com wrote:

Dear Openflipper developer, Suppose we have built up a plugin, but we want to split it into a classes and other slaved ones. Every inherits from QObject, BaseInterface, LoggingInterface, StatusbarInterface, RPCInterface such that they can call other plugin functions, like log, rpc::callFunction, by themselves.

This setup is fine. Usually we also split the functionality into basic plugins. You have to put the plugins into separate folders at OpenFlippers top level directory. Additionally you have to make sure, that they have different names (especially the plugin name returned has to be different).

You can only have one class handling the interfaces in your plugin. All other classes can be derived from QObject but have to communicate to the core via the main plugin class (But you can connect the signals of your subclass directly to the signals of your ain class).

The problem is that we found such design does not work, because they can not work as we imagine;

Do you get any error message?

Only the primary one works fine.

Take a look at the log window. When OpenFlipper starts, it shows which plugins get loaded in the log window. Check for messages regarding plugins that are not loaded. If you use linux, you can start OpenFlipper with the command line option "-c" which will print the full log to your console.

Best, Jan Möbius