THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 03/09/2008 at 03:40, xxxxxxxx wrote:
Cinema 4D Version: 9.603
Platform: Windows ; Mac OSX ;
Language(s) : C++ ;
I have a file type for which I want to:
- generate a thumbnail in the Content Browser
- support drag/drop into the Material Manager
I can write a BitmapLoaderData or a SceneLoaderData for this, but if they are both registered, only the bitmap loader will get called - returning TRUE for BitmapLoaderData::Identify hides the scene loader (obviously). Since C4D now thinks the file is a bitmap, it creates a C4D material when a file is drag/dropped. That is not the desired result, since the file is one of my own materials, which I want to import into the Material Manager. So fine, just don't provide the bitmap loader - but how to generate a thumbnail in the Content Browser using a SceneLoaderData?
Regarding SceneLoaderData - drag/drop using this works fine from the Content Browser, which is registered using PLUGINFLAG_SCENELOADER_MERGEORIGINAL. However, drag/drop from another source (i.e. explorer/finder) always results in C4D opening a new document, regardless of the plugin's MERGEORIGINAL specification. Is there any way to prevent this new document being created?
Does anyone have a recommendation on other ways of dealing with this scenario? Optimally, there would be a third kind of loader...something simple which would work like BitmapLoaderData, but which would also get a notification when dropped/imported into C4D, allowing the implementer to perform the appropriate action.