--- In [email protected], "utaloki" <[EMAIL PROTECTED]> wrote: > > > --- In [email protected], "brucexs" <[EMAIL PROTECTED]> wrote: > > > > > I have put off permanently upgrading powerpro because of this new > > > syntax. > > > SNIP<< > > However, after upgrading, you may have to go to advanced tab, turn > > off "use standard configuration", and then go to characters tab and > Bad expression: expecting operator at > "timer"" is ready:" > input "Minutes until ""timer"" is ready:"
Sorry, this one is my fault. I removed what I thought was an unused feature to have double quotes, as in ""timer"", escape the " when I added more general escape chars. I will add a switch for backwards compatibilty to allow you to turn it back on. . > Command separator: < > Prompt for input with: ? > action: If > (not anywindow "*Outlook Express*")<c:\utils\taskill msmsgs.exe > > ERROR MESSAGE FROM PPro: > > Bad expression: expecting operator at > :\utils\taskill msmsgs.exe > (not anywindow "*Outlook Express*")<c:\utils\taskill msmsgs.exe If your command separate is < and this is in a command list (not a file where it would never have worked properly), then I cannot explain this error. It worked fine when I tried it. The recommendation now is to use cr for separating commands in more command box, but I know this would be some trouble for you to change. The < should still work in command lists. 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/
