THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 27/04/2011 at 10:02, xxxxxxxx wrote:
Cinema 4D Version: R12
Platform: Windows ; Mac ; Mac OSX ;
I've noticed that in R12, when saving a file over an existing file, when you click on the "Save" button in the file selector dialog box, you don't get an alert dialog asking you to confirm that you want to overwrite the file.
Is this a bug in R12's Filename::FileSelect() function, or do I need to set some kind of flag in my code? In previous versions the alert dialog automatically pops up.
On 28/04/2011 at 07:45, xxxxxxxx wrote:
I can confirm this. In which version is this still working? I tested R12 and R11.5.
On 28/04/2011 at 07:56, xxxxxxxx wrote:
I just checked R11.004 on Mac and it's working there.
On 28/04/2011 at 08:00, xxxxxxxx wrote:
Ok, thanks. I will forward this to the developers.
On 28/04/2011 at 08:05, xxxxxxxx wrote:
On 29/04/2011 at 06:40, xxxxxxxx wrote:
Have you passed a file type extension string in FileSelect()? This is necessary to make it work.
Something like this:
fn.FileSelect(FILESELECTTYPE_ANYTHING, FILESELECT_SAVE, "Save", "bmp")
On 29/04/2011 at 07:05, xxxxxxxx wrote:
In my code I'm only passing the title string to FileSelect().
... to set the file type extension.
In R12 do I need to do both, pass the file type extension string in FileSelect() and use SetSuffix()? Or, do I only have to use SetSuffix() for versions prior to R12?
My code is using preprocessor directives:
#if API_VERSION < 12000
... and I'm calling SetSuffix() after the #endif.
On 29/04/2011 at 07:43, xxxxxxxx wrote:
OK, passing the file type extension string for R12 does bring up the warning alert about name conflicts, but there still seems to be a bug, in that the file selector dialog closes out before the warning alert pops up.
This shouldn't happen because if users do not want to save over the existing file, then the file selector dialog should stay open so they can go back and rename it.
The way it is now, users will have to call the export again from the beginning if they don't want to overwrite an existing file.
I only tested this on Mac R12.021.