How to track down resource errors?

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 19/03/2010 at 09:09, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   11 
Platform:      Mac OSX  ; 
Language(s) :     C++  ;

---------
I have made a change in a resource file, and now all the plugins in this package refuses to load their resources with the error message:

Unable to open file
/A..../tralala.res

The files do exist at the given location, though they are named Tralala.res. Renaming them to lowercase doesn't change the issue.

The very funny thing is that most of the affected plugins had neither code nor resource changes... any hint what could cause this?

Any tips how to track that systematically down?

Thanks

Kabe

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 19/03/2010 at 10:28, xxxxxxxx wrote:

It's difficult to say, because it depends on the change you made. I find these files to be incredibly sensitive to the syntax. For example, I changed a parameter from a REAL to a LONG, but left a flag at 'MIN 0.0;'. The resource file failed as a result. Changing it to 'MIN 0;' fixed it. All I can suggest is a very careful look at the change and compare it to the SDK. You will find some tiny error that causes the failure.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 20/03/2010 at 11:58, xxxxxxxx wrote:

Yeah, I know... what I would like to learn if there is any more systematic way to check error.
Validating syntax by wetware isn't exactly the most efficient way to work...

Kabe

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 20/03/2010 at 12:17, xxxxxxxx wrote:

try commenting out certain parts to see if the error goes away.  narrow it down.   Then at least you can get a better idea as to where in the .res file the problem is.

HTH,

~Shawn

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 20/03/2010 at 12:48, xxxxxxxx wrote:

Hi Kabe,

could be that the executable you build is not output into the right directory and you now have two .cdls (or .dylibs) with the same name somewhere in the plugins folder (maybe you accidently copied the cdl or changed the output path) and the misplaced executable is called first. It may be a good idea searching the whole plugins folder for .cdls (or .dylibs) and make sure this isn´t the case (and in case of course remove the double .cdl).

Just an idea.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 20/03/2010 at 13:14, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Yeah, I know... what I would like to learn if there is any more systematic way to check error.
Validating syntax by wetware isn't exactly the most efficient way to work...

Kabe

Basically the best advice I can give you is using a version control system (Perforce, git, mercurial, etc.) - even if you're the only one working on your code. That 's the easiest way to recognize what really changed and what might have caused a problem, as these version control systems contain the necessary tools to diff and merge changes (and also to revert changes).

Best regards,

Wilfried Behne

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 21/03/2010 at 06:33, xxxxxxxx wrote:

Though I agree with you , the question was not what has changed (that was indeed clear), but what caused this specific error.

The error message is not very helpful to identify what exactly went wrong, and this is just one of many examples, where it comes down to guesswork to corner the culprit.

Take for instance the RegisterTagPlugin(). There is a lot that an go wrong at this level, and all we get back is if it worked or not. Of course on the long run we all develop some routine to check the things that have gone wrong the last time, but knowing the symptoms and their cure would help...

Kabe

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 12/05/2010 at 09:50, xxxxxxxx wrote:

Apparently on a Mac, " t ralala.res" != " T ralala.res" (filenames are case-sensitive).

Aside from that issue (that I just ran into myself), I'm now getting other "read error on line xx" problems on the Mac, that were no problem on the PC.. sigh.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 14/05/2010 at 07:41, xxxxxxxx wrote:

Originally posted by xxxxxxxx

...Aside from that issue (that I just ran into myself), I'm now getting other "read error on line xx" problems on the Mac, that were no problem on the PC.. sigh.

...ok, this was just another case-sensitive filename issue - I had to rename both the .res files AND the .h files to start with a lower-case 't' instead of upper-case.

The funny thing is that my Riptide Pro plugin has had this 'bug' for more than a year (erm.. since whenever it _became_ a bug, on the Mac) - and noone has yet reported it. I guess none of my Mac users use the Export Mask Tag in that plugin... interesting.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 14/05/2010 at 08:49, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Originally posted by xxxxxxxx

...Aside from that issue (that I just ran into myself), I'm now getting other "read error on line xx" problems on the Mac, that were no problem on the PC.. sigh.

...ok, this was just another case-sensitive filename issue - I had to rename both the .res files AND the .h files to start with a lower-case 't' instead of upper-case.

The funny thing is that my Riptide Pro plugin has had this 'bug' for more than a year (erm.. since whenever it _became_ a bug, on the Mac) - and noone has yet reported it. I guess none of my Mac users use the Export Mask Tag in that plugin... interesting.

Please note, that MacOS by default doesn't use a case-sensitive filesystem (and therefore avoids these problems). You have to choose that in the disc utility explicitly when (re-)formating a drive.

Best regards,

Wilfried Behne

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 14/05/2010 at 12:24, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Please note, that MacOS by default doesn't use a case-sensitive filesystem (and therefore avoids these problems). You have to choose that in the disc utility explicitly when (re-)formating a drive.

Best regards,

Wilfried Behne

Aha - thanks - I'm not really a Mac guy, so I didn't know that. I'm now compiling on a new system, so I guess it got set up that way.

If there any way to disable that, short of re-formatting?

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 14/05/2010 at 14:36, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Aha - thanks - I'm not really a Mac guy, so I didn't know that. I'm now compiling on a new system, so I guess it got set up that way.

If there any way to disable that, short of re-formatting?

I'm not aware of any "switch" or utility to change that on the fly.

Best regards,

Wilfried Behne