Line break in Messageboxes?
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 24/09/2008 at 05:33, xxxxxxxx wrote:
\n should work.
GeOutString(GeLoadString(MY_ID)+"\n", GEMB_OK)
This does not work?
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 24/09/2008 at 11:48, xxxxxxxx wrote:
I've not seen it work on Mac but it does work on Windows.
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 24/09/2008 at 15:07, xxxxxxxx wrote:
No, it does not.
When I put "\n" into the text, it just prints "\n" into the message box. It's not replaced by a line break
Well, it's not too dramatic. Would just have been nice.
Greetings,
Jack -
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 24/09/2008 at 15:34, xxxxxxxx wrote:
Oh, yes it does!
At least up to R11 for sure. But I use MessageDialog(). Here is a line of code:
MessageDialog(GeLoadString(IPPERR_EXISTFILE_TEXT)+"\n""+newFN.GetFileString()+""");
On Windows, this prints as two lines in the dialog. Can't check this one in R11 since TreeView right-click context menus aren't working (darn - post to come). Maybe a difference between MessageDialog() and GeOutString() perhaps?
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 27/09/2008 at 02:18, xxxxxxxx wrote:
Hey, you are right!
But it only works if I insert the "\n" in my Code. If the string loaded via GeLoadString() contains "\n" it's being ignored. Strange...
Greetings,
Jack -
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 27/09/2008 at 10:55, xxxxxxxx wrote:
GeLoadString() might be stripping EOL characters (?). You could try the Unicode \uXXXX equivalent and see if that passes through unscathed.
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 19/04/2010 at 05:31, xxxxxxxx wrote:
I'm at exact the same issue right now, are there any news on this?
I'm loading error messages from resources. It works when using Windows CRLFs to separate lines, but I would consider this as an ugly hack:
MY_ERRORDLG_MESSAGE "This works in Mac and Windows
if divided with CR+LF but it's fugly";The correct way would be to use the Unicode Line Separator (U+2028) like this:
MY_ERRORDLG_MESSAGE "This works in Mac\u2028but not on Windows!";
Ayn third option that I've overlooked?
Kabe
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 24/04/2010 at 06:59, xxxxxxxx wrote:
Howdy,
Have you tried using the "\u000D" for carriage return (CR)?
Adios,
Cactus Dan -
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 26/04/2010 at 00:54, xxxxxxxx wrote:
No, I have not - as it's defined as legacy in Unicode.
It actually does work though, thanks.
Kabe
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 26/04/2010 at 05:35, xxxxxxxx wrote:
Please use the vertical bar sign "|" to seperate lines, for example "First Line|Second Line".
cheers,
Matthias