>
> Suppose dde wants to callback with a string that contains
> newlines. dde doesn;t know the name of a variable, all it knows
is
> some script to invoke, with the result string as an argument. I
tell
> user to provide callback definition in this form
>
> ?$.scriptname("#")$
>
> and I'll stick the result in the place where I encounter the
insertion
> point, namely #.
>
> But if I put an actual newline in beetween quotes, and send command
> back to PowerPro, pp sees two lines, not one.
YOu really have a double problem in the above
- send a string with newlines
- if the person is using an escape char and it happens to appear in
DDE string (or if quote appears in string) don't screw up DDE-
returned string
I think you can use something like this
esc(?0x19stuff0x18nmorestuff0x19,"0x18")
Which is for stuff<newline>morestuff
Don't put 0x18, rather put the actual hex character. Same for
0x19. YOu may have to experiment with others less then 0x20, but I
think these will work.
PowerPro has a subset of this problem with quotes in captions for
windows hooks and above is approach it uses (it generates a script
callback internally for such hooks).
Attention: PowerPro's Web site has moved: http://www.ppro.org
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/power-pro/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
