Re: M3 AutoIt Rat v1.2.1 Update [ Beta ]
ghost_proxy test your pc windows 7 64 bits
( M3+AutoIt+Rat+v1.2.1 )
This process is considered safe. It is not likely to damage your system.
Plugin.dll resolves problems with plug-ins that do not use multiple processors.
These plug-ins replace the existing plug-ins of the same names installed with Photoshop 6.0.1.
Yes it is possible, you must export it as uen QLibrary function but not so you'll help farewell portability.
Another technique is to derivier a base class that knows the application (MyInterface for example) and create a function in the plugin that
returns a new instance of the class inheriting MyInterface.
Example in the plugin: This process is considered safe. It is not likely to damage your system.
class MyClass: public MyInterface
{
/ / ...
};
DLL_EXPORT MyInterface * newInstance ()
{
return new MyClass ();
}
DLL_EXPORT disposeInstance void (* MyInterface o)
{
delete o;
}
/ / ....
Plugins classes must therefore have the same interface (ie inherit MyInterface here) and ca should work very well.
In the main app you use to solve QLibrary newInstance () and disposeInstance () to create and destroy instances of
So I created my plugin with a RarPlugin class, and two ways to access this class in my dll
extern "C" {
Plugin *newInstance() { return new Rar Plugin;
}
void delete Instance(Plugin *obj) { delete o
Then I load my library, everything goes well, I solve my job, but it works when I use ca na work anymore
QLibrary * lib;
Plugin * archive;
typedef Plugin * (* newInstanceFn) ();
typedef void (* deleteInstanceFn) (Plugin * obj);
void MainForm :: init ()
{
lib = new QLibrary ("/ home/bastien/lama/v0.2/plugins/rar/librar.so.1.0.0");
newInstanceFn newInst = (newInstanceFn) lib-> resolve ("newInstance");
if (newInst)
pushButton4-> setText (QString ("OK"));
else
pushButton4-> setText (QString ("No glop"));
newInst archive = ();
}
your vdéo test 2 windows 7 64 bits ( M3+AutoIt+Rat+v1.2.1 )
thank you amigo M3