Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 20/04/2010 at 07:39, xxxxxxxx wrote:
User Information: Cinema 4D Version: 11.5 Platform: Windows ; Language(s) : C++ ;
--------- Like the Mac version the Windows version should support the Unicode Line Separator (U+2028) for introducing linebreaks in resources like this:
MY_ERRORDLG_MESSAGE "This works in Mac\u2028but not on Windows!";
On 20/04/2010 at 10:01, xxxxxxxx wrote:
Add vote ^^
On 20/04/2010 at 10:49, xxxxxxxx wrote:
have you tried \r\n or just \r ?
Edit: oops, sorry, I thought it worked on win but not on mac but that´s the other way round actually. So scratch that.
On 21/04/2010 at 02:24, xxxxxxxx wrote:
As already pointed out in another thread, the only thing that AFAIK does currently work on a cross plattform way is to add a Windows-Style CRLF like this:
MY_ERRORDLG_MESSAGE "This works in Mac and Windows, but boy is it fugly!";
Kabe
On 21/04/2010 at 06:03, xxxxxxxx wrote:
I'll forward the issue.
cheers, Matthias
On 22/04/2010 at 07:40, xxxxxxxx wrote:
For the time being, I see only one workaround: In the .str file, write:
MY_ERRORDLG_MESSAGE "This works on Mac#as well as on Windows!";
In your code, do e.g.:
String ErrMsg = GeLoadString(MY_ERRORDLG_MESSAGE, "\n");
Cheers, Jack
On 27/04/2010 at 03:24, xxxxxxxx wrote:
Actually Cactus Dan posted another workaround, which seems to work on both Mac & Windows:
Use "/u000d" for CR:
MY_ERRORDLG_MESSAGE "This works on Mac/u000das well as on Windows!";
On 27/04/2010 at 13:02, xxxxxxxx wrote:
Please use the vertical bar sign "|" to seperate lines, for example "First Line|Second Line".
On 28/04/2010 at 01:13, xxxxxxxx wrote:
AAARRRGH, why is Maxon introducing another *non-standard* way to do this?
Maxon defined that Unicode should be used for signs outside the standard ASCII range. The vertical bar is a standard ASCII char in the 7-Bit range, which should not have such a side effect IMO!
I would consider this behavior as a bug.