Macro
Gary W. Shanafelt
A very helpful WP8 macro is ATTRIB.WCM which does neat things like
switching between underlining or italics, or endnotes and footnotes in a
document. When I run it in WP10, I get a series of error messages.
Does anyone have a WP10-compatible version of this macro? Or, if not,
can anyone recommend a source of information for programming WP10
macros, so I can fix it myself? Thanks!
--
Gary W. Shanafelt
http://cs1.mcm.edu/~gshan
Charles Rossiter
Gary,
Have you tried editing the macro in WPWin10, adding a space, and
re-compiling it?
There is a macro Replace.wcm (or very similar name) on Barry
MacDonnell's site which lets a user replace various font codes
by others. http://home.earthlink.net/~wptoolbox
There are standard Corel macro footend.wcm and endfoot.wcm which switch
between footnotes and endnotes.
--
Charles Rossiter
(South Africa)
Volunteer C_Tech
{Please reply to group only}
PerfectScript
The "error messages" may be "warnings" and not errors. Look at the
messages closely and see if they are "errors" or "warnings". If they
are warnings, then you can ignore them, and you will only get them once,
the first time you play the macro, and never again.
--
-J Dan Broadhead-
perfectscript _@_ bigfoot.com
(remove " " and "_")
Gary W. Shanafelt
There are a number of warnings, like "US" language should be "EN"
language. Then come a large number of syntax errors. These are terms
which are referenced but not defined, but then the user is told to check
a different line. For example, one syntax error is that a FONTVERYLARGE
is referenced on line 303 but was not defined. There follows a
statement to check macro file attrib.wcm line 485, character 1. This
line makes no seeming reference to anything, and is starts with
<* EOF *>, with character 1 being "<". Again, any book references on
how to program WP10 macros? ...
PerfectScript wrote:
>The "error messages" may be "warnings" and not errors. Look at the
>messages closely and see if they are "errors" or "warnings". If they
>are warnings, then you can ignore them, and you will only get them once,
>the first time you play the macro, and never again.
>
>
>
>
--
Gary W. Shanafelt
http://cs1.mcm.edu/~gshan
PerfectScript
For "US" in the Application command, change it to "EN".
The FontVeryLarge command existed (though it was obsolete) in WP8, but
does not exist in WP9. Some other command will need to be used.
Sicne there is no such command now, the macro system then assumes that
it must be the name of a label defined within the macro file itself.
The <* EOF *> line means that it found the end of the macro file before
it found the label it was looking for.
Unless you are familiar enough with the WP commands, it seems that there
are enough errors that it might be difficult to fix it yourself.
Given specific information about each error, people here may be able to
help on each specific problem.
For the FontVeryLarge command, I see that there is a FontVeryLargeToggle
command now. The FontVeryLarge command was used to turn on or off the
very large attribute. The FontVeryLargeToggle will toggle the very
large attribute from on to off, or off to on, but cannot be used to
specifically turn it on or off. I'm not that familiar with the WP
commands, but I found the AttributeRelativeSize command, which accepts a
value of VeryLarge!, and others. So It seems that you could use
AttributeRelativeSize(VeryLarge!) to replace FontVeryLarge(on!), and
AttributeRelativeSize(Normal!) to replace FontVeryLarge(off!).
I used the macro help in WP to look up FontVeryLargeToggle, and it
referenced AttributeRelativeSizeToggle, and in the command list next to
AttributeRelativeSizeToggle, was AttributeRelativeSize.
One of the easiest ways to find the macro help, is to click on the
"Commands" button on the Macro toolbar when editting a macro. This will
bring up a list of macro commands. Then you can scroll through the list
of commands, and right click the moouse on the command you want help on.
Maybe we can help you fix the other problems in this macro, or maybe you
can just use the macro that Charles suggested.
--
-J Dan Broadhead-
perfectscript _@_ bigfoot.com
(remove " " and "_")
Gary W. Shanafelt
Thanks for the information. I guess I will try some of your suggestions
and see what happens.
Here are some of the lines with the obsolete commands, to give you more
of a flavor of what I've got to work with:
302 CaseOf "Small": FontSmall (vState)
303 CaseOf "Large": FontLarge (vState)
303 CaseOf "VeryLarge": FontVeryLarge (vState)
305 FontExtraLarge (vState)
And examples of two "warning" statements (which I guess I can ignore for
the moment):
A 'Warning' was detected during the compilation of your PerfectScript macro.
The command 'REGIONGETSELECTEDTEXT' is now a function. The procedure
call format is obsolete, but should continue to operate 'as is' for now.
To call it as a function, move this first parameter outside the
parameter list, and assign the return value from 'REGIONGETSELECTEDTEXT'
RegionGetSelectedText (vFrom[1];"menu.rAttrFrom")
|
Check macro file 'Attrib.wcm': line 325, character 30.
A 'Warning' was detected during the compilation of your PerfectScript macro.
The command 'REGIONGETSELECTEDTEXT' is now a function. The procedure
call format is obsolete, but should continue to operate 'as is' for now.
To call it as a function, move this first parameter outside the
parameter list, and assign the return value from 'REGIONGETSELECTEDTEXT'
to it using the ':=' operator.
RegionGetWindowText (vBeg;"menu.rBeg")
|
Check macro file 'Attrib.wcm': line 386, character 27.
PerfectScript wrote:
--
Gary W. Shanafelt
http://cs1.mcm.edu/~gshan
PerfectScript
Try these suggestions that I have interspersed below:
> Here are some of the lines with the obsolete commands, to give you more
> of a flavor of what I've got to work with:
>
> 302 CaseOf "Small": FontSmall (vState)
> 303 CaseOf "Large": FontLarge (vState)
> 303 CaseOf "VeryLarge": FontVeryLarge (vState)
>
> 305 FontExtraLarge (vState)
Obsolete commands will only issue warnings, which you can ignore. But I
suspect that for these FontSmall, FontLarge, FontVeryLarge and
FontExtraLarge commands, that these don't exist at all, so these are
probably errors, and you will need to replace them.
Earlier I mentioned the AttributeRelativeSize command, which accepts a
parameter to specify the size you want, which is ExtraLarge!,
VeryLarge!, Large!, Small!, Fine! and NormalSize!.
The old commands would accept a parameter of on! and off!. From your
sample code, it looks like the state was being placed into the variable
vState (a values of 0 or 1 were probably being assigned as equevalents
for the off! and on! values).
You will need to rework this section of code, and where vState was being
set to 0 of off!, you can set it to NormalSize! or 5. And where vState
was being set to 1 or on!, you will need to set it to one of the font
sizes that is appropriate for the proper size. The values like Large!,
etc, are really just numeric values with names, and you can pass the
number value instead:
ExtraLarge! = 0
VeryLarge! = 1
Large! = 2
Small! = 3
Fine! = 4
NormalSize! = 5
If you could include the code from the macro where these errors occur,
we could figure out how to rewrite this section.
Becore these "CaseOf" commands, there will be a "Switch" command, and
after, there will be a "EndSwitch" command.
Include all the code from the "Switch" to the "EndSwitch".
And, somewhere before the Switch, there will be a command that assignes
a value to vState. Include that code as well.
> And examples of two "warning" statements (which I guess I can ignore for
> the moment):
>
> A 'Warning' was detected during the compilation of your PerfectScript macro.
>
> The command 'REGIONGETSELECTEDTEXT' is now a function. The procedure
> call format is obsolete, but should continue to operate 'as is' for now.
> To call it as a function, move this first parameter outside the
> parameter list, and assign the return value from 'REGIONGETSELECTEDTEXT'
>
> RegionGetSelectedText (vFrom[1];"menu.rAttrFrom")
>
>
> Check macro file 'Attrib.wcm': line 325, character 30.
>
For this command, call it like this now:
vFrom[1] = RegionGetSelectedText ("menu.rAttrFrom")
> A 'Warning' was detected during the compilation of your PerfectScript macro.
>
> The command 'REGIONGETSELECTEDTEXT' is now a function. The procedure
> call format is obsolete, but should continue to operate 'as is' for now.
> To call it as a function, move this first parameter outside the
> parameter list, and assign the return value from 'REGIONGETSELECTEDTEXT'
> to it using the ':=' operator.
>
> RegionGetWindowText (vBeg;"menu.rBeg")
> |
>
> Check macro file 'Attrib.wcm': line 386, character 27.
>
Same as above - For this command, call it like this now:
vBeg = RegionGetWindowsText ("menu.rBeg")
--
-J Dan Broadhead-
perfectscript _@_ bigfoot.com
(remove " " and "_")
> PerfectScript wrote: