>
> I like your ?c..c implementation, and the ESC() may look more like
> that, but the processing would be done at the time of the function
> processing. Think of ESC() as a function and not a
> conversion/translation like ?c..c or &().
I don't understand how ESC differs from ?c...c or what you mean
by "function processing".
Ignoring &(), the processing of an expression means that tokens like
strings always have to be parsed before calling functions.
PowerPro's parsing is not designed to allow functions calls to
determine how to parse the following characters.
Thats what setstring is a completely separate statement.
But anyway, I don't understand how ESC would accomplish anthig
different from ESC, even if it were possible to implement.
>
> I know you've stopped revisions; but if off the top of your head
you
> think the idea might work, let me know and I'll freeze my
development
> until you have time to look at the feasiblilty.
>
> I hope this idea works!
>
> Ted
>
>
>
>
>
> Ignore the below if you've already fallen asleep:
>
> My ESC() Command in Script looks like:
>
> ; Save this to pprx.powerpro, double click on the filename from
> ; explorer
> ; However, this shouldn't work until you click on a PowerPro bar
>
> ; Using StandardConfiguration
>
> ;=====================================================
> ; Watch for yahoo line breaks because I'm not using \+
> ; because I'm using Exec QuoteEscape OFF
> ;=====================================================
>
> Exec QuoteEscape ON
> GLOBAL fn="C:\New TEMP\test.txt"
>
> MESSAGEBOX(??ok?,??My filename is :[EMAIL PROTECTED](??\n?)++??"?
> ++FILE.name(fn)++??"?,??Exec QuoteEscape ON?)
>
>
> Exec QuoteEscape OFF
> fn="C:\New TEMP\test.txt"
>
> ; Could have done this with ", but demonstrating the EVENT build
> WIN.Debug(??My filename is :[EMAIL PROTECTED](??\n?)++??"?++FILE.name
(fn)
> ++??"?)
>
> WIN.Debug("visible=",VISIBLEWINDOW(??
> =powerpro?),"active=",ACTIVEWINDOW(??=powerpro?))
>
> MESSAGEBOX(??ok?,??My filename is :[EMAIL PROTECTED](??\n?)++??"?
> ++FILE.name(fn)++??"?,??Exec QuoteEscape OFF?)
>
> ; QUIT
>
> ; Note, I can cut and paste the above straight into the Event...
>
> EVENT.Create(2,10,"EVENT.DestroyThis"[EMAIL PROTECTED](??\r?)++MESSAGEBOX
(??
> ok?,??My filename is (from event) :[EMAIL PROTECTED](??\n?)++??"?
> ++FILE.name(fn)++??"[EMAIL PROTECTED](??\r?)++??Active=?++ACTIVEWINDOW
(??
> =powerpro?),??Exec QuoteEscape OFF?),"ACTIVEWINDOW(??=powerpro?)")
>
> ; However, you may have noticed the event "fired" prematurely????
>
> ; Hopefully you made it this far and...
>
> Exec QuoteEscape ON
>
> QUIT
>
>
> @ESC
> Exec QuoteEscape ON
> LOCAL a=&("\""++arg(1)++"\"")
> Exec QuoteEscape OFF
> ; WIN.Debug(a)
> QUIT(a)
>
>
>
>
>
> The above is very useable, but expensive processing and requires
> extra ?c..c when using a script to evaluate ESC() in an event.
> Additionally, if my script errors, sometimes the Exec QuoteEscape
is
> ON and I have to keep manually turning it off. This is why I think
a
> function by you would be better.
>
> Although this proposal doesn't simplify the event command but very
> slightly IMO, it makes events look more like regular commands.
>
> But most importantly, everything else is greatly simplified!
>
> Sorry about the long post, especially if the answer is no.
------------------------ Yahoo! Groups Sponsor --------------------~-->
Yahoo! Domains - Claim yours for only $14.70
http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/JV_rlB/TM
--------------------------------------------------------------------~->
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/
