> I've messed around with many parts of the DOC without going
> section-by-section, partly because IMO it wasn't organized logically

in the
> first place. To track changes use the Word revision tracker. I 
explained how
> at the end of the DOC, where I have some other notes.

This is a lot of work and I'd be pleased to include in future 
versions of the PowerPro zip file.

It looks like you stated from the .doc in 3.8 or an older beta.  How 
had you seen updating for 3.9.  I have two things I want to do yet 
for 3.9:  
- add section on CL
- go through and change examples to get rid of &()

I'll also be happy to send you the rtf source and the web help source 
if you wanted to work on them.

Here are the answers to the questions you posed at the end:

e sources and my eternal gratitude will be your reward :)



THANX

 1) to Vladimir aka Ajax <[EMAIL PROTECTED]> for help in translation.
 2) to Bruce Switzer for PowerPro
 3) to Ergo for promoting PowerPro to me :)
 4) to BuG and Ergo for fileforum.ru where all russian PowerPro fans 
are.
 5) to all people that sent me bug-reports and wishes.



Are these obsolete?
*Keys

Yes, the {param} etc are obsolete.  I agree they should be removed.

Why is there a *Script command?
The purpose of scripting is automation, i.e.executing a series of 
commands, preferably conditionally.  




The Edit list item dialog's Action edit box is single-line, thus 
defeating the purpose (unless PowerPro has some undocumented command 
concatenation syntax like the DOS &). Eg What is the point of 
entering an If or For action in a single-line box?
The *Script command is further made redundant by MoreCommandsAsScript.
IMO this and some of the obsolete features lying around like *Script 
assign shouldn't be in the  main body of the manual but in an 
appendix.


Yes, the *Script command reflects the path that led to scripting as 
it now exists.  As far as the GUI interface goes, if you want to use 
it for entering scripting, then enter the rest of the command in the 
parameters section
*Script
if
(expression) do

In fact, you can enter the command in the first line:
if (expression) do

I guess I am assuming that anyone that does any serious scripting 
will use files.

I think you still need the script command somehow documented in the 
main text, or at least the if, jump, etc.   Also there is *script 
setpath.  





------------------------ 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/
 

Reply via email to