hi,
I was trying to create a multithreaded plug-in but call to
gimp_image_duplicate from worker thread results in the following
message and worker thread deadlocks.
(webexport:4097): LibGimp-WARNING **: unexpected proc return message
received (should not happen)
What am I doing wrong?
On Wed, 2007-05-16 at 18:12 +0300, Aurimas Juška wrote:
hi,
I was trying to create a multithreaded plug-in but call to
gimp_image_duplicate from worker thread results in the following
message and worker thread deadlocks.
(webexport:4097): LibGimp-WARNING **: unexpected proc return message
guys + gals,
for all of you who missed our presentation at the lgm,
I have converted the talk into blog entries.
The first part (of three) is online now:
http://www.mmiworks.net/eng/publications/2007/05/lgm-gimp-project-
overview.html
ps Alexandre Prokoudine: you can link to these as the
Hi list,
I know that some data of plugin can be stored in GIMP's pool by the function
below:
gimp_set_data (some_data, mydata, sizeof (MyData));
But how big can this data be? If I want to store a very big data, say, a
color mask of
an image, what should I do? Is it advisable to save this kind
tao frank ([EMAIL PROTECTED]) wrote:
I know that some data of plugin can be stored in GIMP's pool by the function
below:
gimp_set_data (some_data, mydata, sizeof (MyData));
But how big can this data be? If I want to store a very big data, say, a
color mask of an image, what should I do?
2007/5/17, Simon Budig [EMAIL PROTECTED]:
This data gets stored in the RAM and then sits there. Although there is
no limit on the size of this data this functionality is not intended to
store huge amounts of data. It is more about a small struct saving the
preferences of a plugin or similiar
