Re: Bug with "\n" in Display Message Box
Jeff,
> Perhaps creating a wrapper for Clarion's MESSAGE() in a support DLL
> would be the most expedient way to solve this dilemma?
It's an option although using "\ nwhatever" is also. Yes, the space is
noticeable but do users ever actually READ this stuff?<g>
Lee White
Re: Bug with "\n" in Display Message Box
Hi Lee,
> \r is not a problem since it's just a carriage return but \n can be
I would have expected \r to start a new string on the same line so you'd
get overwriting.
What happens if you put this into a variable and use the variable in the
message?
Best regards,
--
Arnor Baldvinsson
Icetips Alta LLC
1 Attachment(s)
Re: Bug with "\n" in Display Message Box
Arnor,
> I would have expected \r to start a new string on the same line so you'd
> get overwriting.
>
> What happens if you put this into a variable and use the variable in the
> message?
Works. From what I've seen \n for newline is the only usage in SB.
Lee White
Re: Bug with "\n" in Display Message Box
Hi Lee,
> Works. From what I've seen \n for newline is the only usage in SB.
Cool!
Best regards,
--
Arnor Baldvinsson
Icetips Alta LLC
Re: Bug with "\n" in Display Message Box
Hi,
Instead of using "\n", why not using another combination which is more
unique, for example: <13,10>
Because I want in my message box:
1. c:\nginx\nginxservice.exe
2. *AND* new lines
At this moment, I guess this is not possible?
Best regards,
Jeffrey Kuijt
1 Attachment(s)
Re: Bug with "\n" in Display Message Box
THANK YOU, Jeff!
(And you, too, chopped liver <g> )
That isn't obscure at all.....
Gonna see if setting it here sticks....
jf
Re: Bug with "\n" in Display Message Box
Jane,
> (And you, too, chopped liver <g> )
Yeah, yeah, whatever!
Oh, and it stuck!
Lee White