Agree, ESC() would occur when ?c..c is done. (I was stuck in an older untested idea before ?c..c)
ESC() is a version of ?c..c that allows escapes while Exec QuoteEscape is OFF. So, how would you do the following with "Exec QuoteEscape OFF" and always OFF without a new command. Exec QuoteEscape OFF c=ESC(\r\n\d008) and get CR LF and hex 08 in the character c, or EVENT.Create(2,10,"EVENT.DestroyThis"++ESC(\r)++Messagebox... and get a CarriageReturn? The key to this idea, is that Exec QuoteEscape is OFF and the only things escaped are what I enclose in the command. No more accidental escapes, because what we want to have escaped is always and only inside ESC() because "Exec QuoteEscape OFF". Sorry, I'm not very good at explaining myself. Ted > 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. ------------------------ Yahoo! Groups Sponsor --------------------~--> Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar. Now with Pop-Up Blocker. Get it for free! http://us.click.yahoo.com/L5YrjA/eSIIAA/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/
