Loading ...
Sorry, an error occurred while loading the content.

WP Mac News 96/08

Expand Messages
  • jrethorst@post.com
    August 1996 Issue 20 WPMac News is a monthly newsletter published for those who use WordPerfect for Macintosh, anyone interested in the product, and those who
    Message 1 of 1 , Dec 7, 2004
    • 0 Attachment
      August 1996 Issue 20 WPMac News is a monthly newsletter published for
      those who use WordPerfect for Macintosh, anyone interested in the
      product, and those who stumble across this newsletter and are
      captivated to read. It contains any late-breaking news, the hottest
      issues from customer support, and extensive coverage of WPMac features.
      Check out this current issue, as well as our past issues. We hope you
      find the News informative, helpful, and even entertaining. Enjoy the
      August issue. I know that you have been eagerly awaiting news
      concerning the Corel WordPerfect release of 3.5. Well, no news
      is....what is the rest of that cliche? The update is coming, we
      promise. It should be available in August. Please know that we are
      working hard to make sure the update releases soon. Keep checking our
      ftp site. We will post the update file as soon as it is available:
      ftp.corel.com/pub/wordperfect/wordperfect/wpmac/updates This is our
      first issue with contributions from our readers!! Check out the tip
      from Michael Blair in the Tips & Tricks section and be sure to take
      some time to admire the macro from Mike Beshara in our Monthly Macros
      section. Lisa Credits Lisa Foster, Editor and Layout LaMar Kirby,
      Graphic Design and Web Master John Rethorst, Mastering Macros WPMac
      Support Team Page Aug 2 96 Writing Tools by Lisa Foster You have used
      them to write your thesis, business proposals, and when you just can’t
      remember from 8th grade English class, if ‘a lot’ is one word or two.
      The following is an explanation, guide, and handbook for the writing
      tools you can’t live without. SPELLER Tools|Speller|Start The Speller
      will spell check the entire document. If you want to check only a small
      portion of the document, highlight that section of text before starting
      the Speller. Page Aug 3 96 Dictionary The Dictionary (USA) file must be
      located in the WordPerfect 3.x|Language folder. If this file has been
      moved, a Dictionary dialog box will appear on screen in place of the
      Speller. This dialog box indicates that WordPerfect can not find your
      Dictionary and is unable to spell check. Simply locate Dictionary (USA)
      in this dialog and click the Open button. Your Speller will open and
      from now on will remember the location of the Dictionary...unless the
      file is moved again. If you can not locate the Dictionary (USA) file,
      it may have been deleted. Reinstall WPMac to reinstate the file. You
      may use other dictionaries. Any installed dictionary found in the
      Language folder can be used to spell check your document. Once the
      Speller dialog is opened, select the dictionary you want to use from
      the Dictionary pull-down menu. Please note that only one dictionary can
      be used at a time to spell check. Page Aug 4 96 How to spell check
      other languages (Spanish, French, etc.)? You must have the dictionary
      for your specified language installed into the Language folder and
      selected from the Dictionary pull-down menu in the Speller dialog. The
      French, German, and Spanish dictionaries will be available in the new
      release of Corel WordPerfect 3.5. User Dictionary The User Dictionary
      (USA) file is also located in your WordPerfect 3.x|Language folder.
      This file contains all of the words you have added to your Speller. It
      is automatically created the first time you click the Add button during
      a spell check. The User Dictionary can not exceed 32K in size. If you
      notice that the Speller is not retaining any of the words you add, the
      User Dictionary may be full. To alleviate this problem, you can merge
      the words from this file into the main Dictionary: Page Aug 5 96 • Open
      the WordPerfect 3.x folder|Language folder. • Double click ST Utility.
      • Select Dictionary (USA) in the dialog that appears on screen. • Click
      the Add from User-Dictionary File button. • Select User Dictionary
      (USA) in the dialog that appears on screen. Words from this file will
      appear on the right-hand side under Modifications. • File|Save. The ST
      Utility will now copy all of the words from the User Dictionary into
      the main Dictionary. • File|Quit. • Drag the User Dictionary (USA) file
      into the Trash. The next time you select Add from within the Speller, a
      new User Dictionary (USA) file will be created. Page Aug 6 96 THESAURUS
      This writing tool is simple and easy to use. Tools|Thesaurus|Look Up If
      you place the cursor in a word or if you select a word, it will appear
      in the Word box and the Thesaurus will automatically show possible
      synonyms or antonyms. You can also type the word you want to look up in
      the Word box. If the word is not contained in the Thesaurus, the normal
      listing of synonyms and antonyms will not appear (you may also hear a
      beep when you click on Look Up). Try looking up a similar word or
      another form of the word. The Thesaurus (USA) file must be located in
      the WordPerfect 3.x|Language folder for the Thesaurus to work
      correctly. Page Aug 7 96 You can look up a word in the Thesaurus when
      WordPerfect is not active. Double click the Thesaurus (USA) icon in the
      Language folder. The ST Utility will open and allow you to type in any
      word, then click on Look Up. GRAMMATIK This tool will identify
      grammatical problems in your document and offer advice on how to
      correct them. Tools|Grammatik|Start Grammatik will check the entire
      document unless you select a portion of text. It will pause at each
      error and wait for your input. Grammatik uses predefined writing styles
      to proofread your document. The writing style you select from the Style
      menu will determine the rule class used to check your text: Page Aug
      8 96 General Unspecified. This option is selected by default.
      Advertising Advertising copy and other marketing literature (informal
      with an emphasis on mechanics and grammar). Business Letter Business
      letters or other writings that require strict interpretation of formal
      grammar. Documentation Manuals and instruction booklets targeted to a
      general audience. Fiction Creative writing with an informal style.
      Journalism Stories and other journalistic pieces where jargon and
      colloquial language are acceptable. Memo Inter-office memos (standard
      formality). Proposal Formal proposals or other long documents that
      should adhere to a conventional, formal grammar style. Report Business
      reports and college papers. Technical Publications or writings that use
      technical vocabulary or complex noun phrases. Page Aug 9 96 If these
      predefined styles do not accommodate the grammatical needs of your
      document, feel free to create your own custom writing style: • Choose
      Custom 1,2, or 3 from the Customize menu in the Grammatik dialog.
      Notice that you can create only three custom styles. • Give your
      writing style a name and select one of the predefined writing styles in
      the Pattern After menu as a template for your new custom style. • Edit.
      • Select a formality level. This determines how strictly style,
      grammar, and mechanical rules will be interpreted. • Customize the
      thresholds: Consecutive nouns The number allowed in a sentence.
      Consecutive prepositional phrases The number allowed in a sentence.
      Long sentence length The number of words allowed in a sentence.
      Page Aug 10 96 Passive sentences (of last 10) The number of occurrences
      of passive voice allowed within 10 sentences. Spell number below or
      equal to The value used to determine if a number should be spelled out
      (nine) or written as a figure (9). Words allowed in split infinitive
      The number of modifiers allowed in split infinitives. • The Rules
      button allows you to select the rules used to check grammar, style, and
      mechanics. • Click Save. Your custom writing style will appear in the
      Style menu. *Hint for Powermacs: If you click on the Tools menu and
      find that Grammatik is grayed out, you need to turn on virtual memory
      (found in the Memory control panel) and then restart your computer.
      They are useful and they are handy. Take some time to check out what
      these writing tools can do for you. Page Aug 11 96 by John Rethorst
      ODDS ’N ENDS Knowing the code As you probably know, you can dig around
      in a document pretty effectively by opening the codes window. As a
      user, you can also leave that window alone. As a scripter, though, you
      can do amazing things with the codes. Say you have a document with
      three different fonts. You want to change one of the fonts from
      Palatino to Times, and leave everything else alone. The font definition
      unfortunately isn’t in a style sheet, so that won’t help. This macro
      will: Page Aug 12 96 Codes (Show) Find Next Code (Forward;Font
      Change);the code name is spelled exactly as you see it in the Find Code
      dialog If (FontName="Palatino") Font Name ("Times") Delete Right;this
      deletes the Palatino font code as long as the codes window is open End
      If Codes (Hide) Note that the two-word “Font Name” is a command, while
      “FontName” all together is a read-only variable. All WP r/o variables
      are named with one word. You can put this script in a Repeat/Until
      (!FindStatusFlag) loop to fix an entire file, since FindStatusFlag
      reflects a code search as well as a text search. Turn display off for a
      big speed enhancement, since the codes window needs to be open for the
      Delete Right command to affect a code rather than a character. Page Aug
      13 96 Run the macro at the top of your file, as finding codes doesn't
      have a wrap-around option. You can send execution to the top of your
      file with Home () or Goto Top of Document. The latter puts the
      insertion point before any codes. If you want to get elegant and test
      first whether the codes window is open, and leave it in that state when
      the macro ends, you could start the script like this: If
      (ShowCodesFlag); if the codes window is open Assign (Var01;1) Else
      Codes (Show) End If and end the macro with: If (!Var01) Codes (Hide)
      End If Page Aug 14 96 Important design concept here: the macro looks
      for a generic font change code, and then tests for the specific font
      name. In this way, you can search for all sorts of stuff in a file, by
      first looking for the type of thing, and then testing for a more exact
      match. Fonts should of course be put in style sheets in the first
      place, but what if you wanted to replace one style itself with another?
      Style sheets won’t help there, but my friend and macro genius Dave
      Moulton did just this with a script written to find the code Style On,
      followed by a test with the variable CurrentStyle and then the command
      Apply Style, in his macro “Manipulate Styles,” featured in the January
      ’95 WPMac News. But I won’t analyze the whole thing here, because a
      habit you’ll want to form to become truly adept at macros is to look at
      the script of any macro you find whose design or operation interests
      you. Some scripts seem daunting at first, but you’ll see that they’re
      made up of parts – labels, loops and such – and the operation of each
      part isn’t hard to understand. Flowchart a script as you read it, and
      the overall structure will become easy to see. Page Aug 15 96 HTML
      Codes WP 3.5 added HTML editing. HTML styles are separate from WP’s
      regular style sheets, a fine idea except when you want to take
      someone’s file full of regular styles and translate them into HTML.
      This sample code assumes that your source file has styles “Heading1,”
      “Heading2,” and “Heading3,” which you want to set to HTML headings 1, 2
      and 3: Goto Top of Document;before any codes Repeat Find Next Code
      (Forward;Style On) If (CurrentStyle="Heading1") HTML Heading (1) End If
      If (CurrentStyle="Heading2") HTML Heading (2) End If If
      (CurrentStyle="Heading3") HTML Heading (3) End If Page Aug 16 96 Until
      (!FindStatusFlag) So the paradigm with codes is, again, find the
      generic code and then test for the specific style, font or whatever.
      Catching errors Given how easy it is to include quote marks where you
      shouldn’t, etc., it’s nice that WP has error-checking for macro
      scripts. You’ve probably already seen the first level of error
      correction: when you save a script, WP parses it, looking for bad
      syntax, misspelled commands, and the like. It underlines what it finds,
      and requires you to fix them before it will save the script as a
      compiled (i.e. ready to run) macro. You can save anything as text, of
      course. Or, if you’re finishing up for the day and can’t figure out
      what’s wrong with one command, you can “comment it out” – put a
      semicolon in front of it, to turn the command into a comment, save the
      script, and leave it. It’ll be there for you tomorrow. If your script
      parses OK but still doesn’t run right, WP has three debugging commands
      to help you sort it out: Page Aug 17 96 Step puts up a window showing
      the macro command that will run next, after you press any key. You can
      thus step through your script one line at a time, until you find the
      one that’s going kablooey. The syntax is: Step (On) and you can change
      the ‘on’ to ‘off’ and leave the command in the script, if you’re going
      back and forth as you debug. Or turn step on only for the troublesome
      part of your code. Speed slows down macro execution, by adding a delay
      between the execution of each line of code. The delay is expressed in
      60ths of a second, so: Speed (60) will put a one-second delay between
      each command. Wait does the same thing but only at the point where it
      occurs in the script. So: Page Aug 18 96 Wait (180) puts a single
      three-second delay into execution, while Step and Speed set the pace of
      things for the rest of the macro, or until another Step or Speed
      command is encountered. You could thus step through one troublesome
      part of your script. Wait is also useful when you put up a Prompt, one
      of the ways of talking with your user. Take a look in the online help,
      and you’ll see that parameters for Prompt include the vertical and
      horizontal coordinates in points/pixels for the message, then the
      title, then the message itself. So an example might be: Prompt
      (75;125;"Sample Prompt";"Are you awake right now? How do you know?")
      Wait (180) End Prompt If a Prompt command isn’t followed at some point
      by an End Prompt command, the window stays on screen until the user
      clicks in the close box, and that’s all the user can do. With an Alert,
      discussed in previous columns, the dialog appears at the center of the
      main Page Aug 19 96 monitor and has an OK button. Menus give the user
      any number of choices, and Confirm posts multiple buttons on the order
      of OK/Cancel or Yes/No/Cancel. Pause can be used for debugging, or for
      the user’s convenience. It’s not the same as Pause Until, which we
      learned in July. That command pauses the macro until a specific
      keystroke occurs, and then resumes execution. Pause simply stops the
      macro until the user chooses the Continue command from the macro menu.
      This can be useful in a number of situations, training for one. Imagine
      that your macro shows some steps in formatting, and then types some
      plain text for the user to practice on. The macro then pauses for the
      user to repeat those steps, after which he or she chooses Continue.
      When we want an error On occasion we plan for an error to occur at some
      point. I call the following script from my OnOpenDocument macro. If
      I’ve launched WP and have an empty Untitled document onscreen, and I
      open an existing document, this macro closes the Untitled doc
      automatically. It makes an exception and does nothing if the front
      window is untitled (the asterisk is a wild card, standing in for any
      string) or if the front window is either of the two that my Page Aug
      20 96 OnStartUp macro calls. Glossary File assigns glossary entries as
      we learned last November; Data sets Citation format, as we saw in May.
      You type the or operator with shift-backslash. On Error (cascade) If
      (FrontWindow="untitled*"|FrontWindow="Glossary
      File"|FrontWindow="Data") Go (end) End If While (Var01=Var02) Select
      Window ("untitled*") If (!DocumentModifyFlag) Close Else Go (cascade)
      End If End While Label (cascade) Cascade Windows Label (end) Page Aug
      21 96 I wanted this to work for multiple untitled and unmodified
      windows, so I put in a While loop, specifying while Var01=Var02 (see
      below for more discussion of the While command). Var01 is always going
      to equal Var02 here, since neither is ever assigned a value. So the
      while loop will repeat forever or until the macro doesn’t find any more
      windows with Untitled as the first part of their name. Then it returns
      an error. That’s why the first line in the script is an error handler,
      sending execution to the Cascade label. This gets execution out of the
      while loop, with a guarantee that there are no more new and untitled
      windows. Other error handling Often enough, we’re not looking for an
      error, but want to send execution in the right direction if one occurs.
      That direction can change depending on where we are in the script. This
      code is the “Save plus Editors” component of my Note Editor macros,
      version 3, an example of letting the macro do the thinking. What it’s
      designed for is saving a footnote editor or an endnote editor (or both,
      if both are open) and saving the editor’s paper – but not other open
      documents. Page Aug 22 96 When the macro starts, it doesn’t know if
      there’s an endnote editor or a footnote editor open. So it tests for
      one by, at the appropriate place in the script, trying to select a
      window with, for example, “footnotes” as part of its name. If there is
      no such window open, WP returns an error. If there were no error
      handler earlier in the script, you’d just get an alert informing you of
      the error, and the macro would quit. But with an error handler,
      execution will go to a specified label if an error occurs. Thus, in
      quasi-macro terms: On Error (Buy Plane Ticket) Ask boss to double your
      salary ; more code Label (Buy Plane Ticket) ; code here will execute if
      boss threw you out the window and here’s some actual code: If
      (NewDocumentFlag) ; untitled doc has never been saved If
      (!DocumentModifyFlag) ; because there's nothing in it End Macro ;
      nothing to do Else ; if anything is in the doc Page Aug 23 96 Save ;
      posts the dialog End Macro ; that's it for us End If End If Assign
      (Var01;FrontWindow) ; we need to remember which window is in front when
      the macro starts SubString Position (Var02;">~Footnotes";FrontWindow) ;
      if we get anything here, the front window is a footnote editor
      SubString Position (Var03;">~Endnotes";FrontWindow) ; or here, an
      endnote editor Call (prompt) ; last subroutine in the script checks for
      unsaved changes in front window, posts prompt, saves, ends prompt ; If
      (Var02|Var03) ; if we have any kind of editor in front Assign
      (Var04;DocVar7) ; get name of paper from a doc variable in the editor
      Else Assign (Var04;Var01) ; if an editor isn't the front window, then
      the paper is. So this if-else statement puts the paper name in Var04 in
      any case End If String Length (Var05;Var04) ; how long is paper name?
      Page Aug 24 96 If (Var05>18) ; if longer than 18 characters SubString
      (Var06;1;18;Var04) ; get first 18 Assign (Var07;"<"$Var06$"…>~") ; add
      carets and ellipsis per our naming convention Else Assign
      (Var07;"<"$Var04$">~") ; just add carets if paper name is short enough
      End If ; If (Var02) ; if footnote editor is in front On Error (paper) ;
      go deal with the paper if you can't find an endnote editor Else ; if
      anything but a footnote editor is in front On Error (footnotes) ; go
      looking for that footnote editor when you're finished here End If
      Select Window (Var07$"Endnotes") ; if there's an endnote editor, get
      it. If not - returns an error - go to 'paper' or 'footnote' labels Call
      (prompt) ; save the window If (Var02) ; if a footnote editor was in
      front when the macro started (it won't be now if we found an endnote
      editor to save) Page Aug 25 96 Go (paper) ; that footnote editor was
      then saved as the first step - saving the active window, so we don't
      need to select it and save it again, as the next subroutine would do
      End If ; Label (footnotes) ; from the error handlers for Var02, if the
      footnote editor wasn't in front On Error (paper) ; we need another
      error handler in case the next command, to select a window, returns an
      error - because there wasn't a footnote editor open Select Window
      (Var07$"Footnotes") ; get footnote window Call (prompt) ; save it ;
      Label (paper) ; error handlers get us here if there's no footnote
      editor open when we look for 1) an endnote editor, or 2) a footnote
      editor Select Window (Var04) ; get the paper - or the original front
      window If (Var02|Var03) ; if the original front window was an editor,
      the paper hasn't been saved Call (prompt) ; save it End If ; Label
      (prompt) If (DocumentModifyFlag) Page Aug 26 96 Prompt
      (ScreenSizeH/2-240;ScreenSizeV/4;"Saving";"Saving changes to
      “"$FrontWindow$"”") ; I like this. Both Lotus 123 and More have a
      saving prompt. ScreenSize stuff puts prompt in window center
      horizontally, third of the way down vertically ("dialog position" per
      Mac interface guidelines, more or less) Save End Prompt End If Return ;
      we got to this subroutine with the Call command Accessing variables
      Often enough, while coding a macro we need to see what’s in a given
      variable – either a r/o or read-write. So WP lets you assign keystrokes
      to variables, just like assigning keyboard equivalents to commands and
      menus. Go to Keyboard in Preferences and, from the pop-up menu at the
      top left, choose Variables. You get a list of every variable in the
      program. The keystroke will type the value of the variable at the
      insertion point, and you can check its value at your convenience.
      Page Aug 27 96 Let’s Let’s get loopy What’s this with the While loop
      above? It’s much like Repeat/Until, but can be more efficient in some
      situations. In the macro above, I could have had line six as “Repeat”
      and line 13 as “Until (!Var01=Var02)” – same difference. Since neither
      Var01 nor Var02 have been assigned anything, the While command will
      always be true, and the Until command would never become true – so the
      macro keeps looping until there’s an error. Since Repeat/Until and
      While differ in the nature of the test, one or the other may be better
      suited to a particular purpose. The third kind of loop WP offers is
      For. This is a little more sophisticated, with the increment that’s
      going to affect the test included in the syntax. The four parameters
      are: variable, initial value, test, and increment. So: For
      (Var01;1;Var01<Var49;Var01+1) [some code here] End For Page Aug 28 96
      will assign Var01 a value of 1, and test whether Var01 is less than
      Var49. If it is (the result is true), Var01 is then assigned the fourth
      parameter (in this case, Var01 is incremented by1), the code between
      the For and End For commands is run, and execution returns to the For
      line. Here’s an example of the three types: Assign (Var49;25) ; Menu
      (Var00;"For/Repeat/While";{"For";"Repeat";"While"}) Case
      (Var00;{1;for;2;repeat;3;while};cancel) ; Label (for) For
      (Var01;1;Var01<Var49;Var01+1) Type (Biff ) End For End Macro ; Label
      (repeat) Repeat Type (Biff ) Page Aug 29 96 Assign (Var01;Var01+1)
      Until (Var01=Var49) End Macro ; Label (while) While (Var01<Var49) Type
      (Biff ) Assign (Var01;Var01+1) End While Three considerations: 1) The
      three loops in this example don’t all produce “Biff” 25 times. The For
      loop tests, increments and then runs, and you get 24 Biffs. The While
      loop has the same test, but it tests, runs and then increments, so you
      get 25. The Repeat/Until loop wouldn’t run at all with the test “Until
      (Var01<Var49)” so the test was modified. 2) the For loop takes a line
      less of code. This means that it may run faster and, when you and the
      other hackers swap fish stories, the trump is doing something with as
      few lines of code as possible. The point of fewer lines is that it’s
      more elegant, plus it might run faster. Page Aug 30 96 3) Depending on
      the code structure you’re up to your neck in, one of the three types
      might run faster. Or have I already mentioned that? Loops at the
      ‘macro’ level We can take this loop/test idea up a level, and have one
      macro execute another if a certain test is met, using either the Run
      command, to execute that other macro right away, or Chain, to run the
      other macro when this macro is finished. If you use the Run command,
      execution returns to the first macro when the second is done – unless
      execution encounters an End Macro command. This is a primary use of
      this command, since macros end anyway when they run out of code. For
      example: ; main macro If (GlobalVar01>10) Run ("moreThan") Else Run
      ("lessThan") End If Page Aug 31 96 Type (Biff ) with the submacros: ;
      moreThan If (GlobalVar01>20) End Macro End If so you’ll get “Biff” in
      your document if GlobalVar01 is 20 or less. Why not put all your code
      in one macro? There’s more than one good reason! A few are: 1) size. My
      Character Styles is a set of 28 macros, totalling over 3000 lines of
      code. Even if it added up to less than 32K, the limit for a macro, it
      would be crazy to try and edit all that code in one script. This is
      partly since WP’s macro editor doesn’t have Find/Change or other
      features that overall use wouldn’t justify, but mainly because a
      manageable size is vital to: Page Aug 32 96 2) good organization.
      Within a single macro, there’s lots of places to put this or that
      little tidbit of code: initialize a variable, set a font, whatever. All
      those little hiding places make them harder to find when you decide to
      change them. With a set of separate, modular and interacting macros
      each with a more specific purpose, editing is easier. You can also save
      generalized versions of these single-purpose macros in: 3) libraries,
      which make easy building blocks for future projects. Starting to put
      things together If you’ve been following my columns since February
      1995, you’ve covered a great deal, but macros may seem more mystifying
      than ever. Even if the examples made sense right away, you still might
      be wondering, “How will I ever learn what all those variables are?” and
      “When will I start to grasp the big picture?” When you think of it,
      questions like these are what everyone has when learning a language:
      Swedish or Thai as well as macros. There just seems to be too much to
      digest. But don’t worry. Learning is a funny endeavor: it rarely takes
      a linear pace. Everything Page Aug 33 96 seems overwhelming for a
      while, and then – presto – parts start to fall into place. Let’s help
      this along with some learning strategy. Like any language, the WP macro
      language has two basic parts: grammar and vocabulary. Grammar, or the
      If/Else, Repeat/Until kinds of structure we’ve learned, is best
      approached by example and practice. Vocabulary, though, can be learned
      either this way or by browsing WP’s online macro help (not the standard
      help file, but “WP Macro Help,” the fourth choice on the balloon help
      menu). Otherwise, a printable list, separated into commands and
      variables, is included in the WP 3.1 and 3.5 ReadMe files. Overall, the
      most effective way to learn code is by studying examples. Now that you
      know how to troubleshoot and write tight loops, we’ll spend the next
      few months dissecting some sophisticated and elegant code. Those
      adjectives will, in short order now, describe the macros you write. * *
      * John Rethorst, author of Teach Yourself WordPerfect, consults macro
      scripts instead of horoscopes. Contents Copyright © 1996 by John
      Rethorst. Used by permission. Page Aug 34 96 Size Window-by Mike
      Beshara, A MACRO MASTER IN THE MAKING “I like this macro a lot, even
      though it's simple. It resizes the top document window to leave some
      space on the right side of the screen so you can easily drag stuff to
      the desktop to make clippings files. As you know, Macintosh
      drag-and-drop essentially gives you an unlimited number of clipboards.
      You simply drag anything you want to cut or delete, to the desktop
      (rather than cutting or deleting it) and then drag the clippings file
      it creates to another document (or later, to the trash). The macro
      works only if you've got your button bar on the left side of the
      screen. Otherwise, you'll have to change the coordinates in the macro
      on where to place the window. Page Aug 35 96 I have this one as my
      "OnOpenDocument" macro, so all my windows are automatically sized and
      placed where I want them when I open or create the document.” Thanks
      for this great macro contribution Mike! Check Box-WordPerfect 3.1 and
      3.5 This macro provides three check box options: n n4 n5 The Check Box
      macro ships with versions 3.1 and 3.5. The Tools|Macro menu will
      display its name. If it is not listed in the Macro menu, it needs to be
      copied into Library (USA). The macro is stored in the Sample Macros
      Read Me file. This document is located in the Document Experts folder
      for version 3.1, and in the Documentation folder for version 3.5.
      Page Aug 36 96 Open Sample Macros Read Me|Edit|Preferences|Librarian.
      Change the Resource to Macros and copy the Check Box macro into Library
      (USA). This macro can also be found in the August Macros Read Me file
      attached to this month’s newsletter. Macro Tip! Some of John Rethorst’s
      hottest macros are now available on our ftp site! We will continue to
      keep this macro site updated with John’s latest and greatest.
      ftp.corel.com/pub/wordperfect/wordperfect/wpmac/macros Attached to this
      month’s newsletter you will find the file, John’s Macros Descriptions.
      This file provides an explanation of each macro. Note: John’s Outlining
      macros, version 5, are currently in beta and should be out within a
      couple of weeks. Page Aug 37 96 We welcome your comments, feedback,
      tips & tricks, and questions you would like to see answered in the News
      at wpmacnews@... (technical support questions will not be
      answered here).You can send any technical support questions to
      wpsupport@.... Allow a 3-4 day turnaround. If you need live phone
      support for a WordPerfect for Macintosh product, reach us at (801)
      765-4020, Priority : $25 fee (800) 861-2070, $2 per minute (900)
      555-3535. I just installed version 3.5 and want to know how to convert
      all of my macros and styles that I used in WPMac 3.1 into 3.5. This one
      is a cinch. All of your styles and macros will convert for you. They
      are saved in the file called, Library (USA). The location of this file:
      System Folder|Preferences|WordPerfect. WPMac versions 3.x, all use this
      same file as storage for styles, macros, button bars, and keyboards.
      So, if you were using any 3.x version and now just installed 3.5, your
      styles and macros will automatically carry over with this file. No work
      to be done on your part. The Tools menu will continue to display all of
      your macros you used with version 3.0 or 3.1. Page Aug 38 96 If using
      WPMac version 2.1, the styles and macros are saved in a file called,
      USA–Private Library. It is saved in the same location as Library (USA).
      You must copy over your macros once the new 3.5 version is installed:
      Launch 3.5|Edit|Preferences|Librarian. Select macros as your Resource.
      Select USA–Private Library from the right-hand pull down menu (may
      currently show as Untitled or the name of the active document). Select
      any macros from the right–hand side that you would like to copy into
      Library (USA) and click on the Copy button. How can I change the
      information that is inserted into the Business Card template? This
      information is gathered from the Personal Information.
      File|Templates|Open. Click the Personal Info button at the bottom of
      this dialog. Change your information and click OK. Reopen the Business
      Card template and your new information will display. Page Aug 39 96 I
      need to place a checkbox in my document. Where can I find one? There
      are four nice check box characters mapped to the Zapf Dingbats font
      (this font does not ship with WordPerfect). Select this font and click
      Insert|Symbols. Click on any one of the check box characters opqr to
      insert them into your document. One other check box option: take a look
      at the Monthly Macros section for a highlight of our Check Box macro.
      Page Aug 40 96 Use the backslash character \ to include parentheses
      with text when using the Type macro command. Normally, parentheses are
      used to designate the beginning and end of text with this macro
      command. So, when you need to incorporate parentheses into the text
      itself, use the backslash character to comment out the proceeding
      character: Type (I will eat anything (that is made with chocolate\))
      Tip from Michael Blair, a proficient WPMac 3.5 user: Using the
      keystroke, Option [ will insert an open smart quote “, and the
      keystroke, ShiftOption [ will insert a close smart quote ”. These are
      helpful keystrokes if you have smart quotes disabled but still find a
      need to use them in your document every now and then. Page Aug41 96
      When creating your own custom labels merge form file, make sure that
      you use the Next Record code. Each label, excluding the first label,
      should have a <Next Record> code placed BEFORE the first Field code.
      Incorrect placement of this code will cause a definite malfunction in
      your merge. CORRECT INCORRECT <Next Record><Field:1> <Field:2>
      <Field:3> <Field:1> <Field:2> <Field:3> <Next Record> When creating a
      standard labels merge form file, let our Labels template do all the
      work for you: File|Templates|Labels. Select your label size through the
      Setup button. Click the Fill button|Merge Codes (Form File)|Quick Setup
      (Field Numbers)|Enter the number of fields you want to merge from your
      data file. The template will automatically format the form file for
      you.Page Aug42 96 Interested in Applescript? You can take a peek at the
      Applescript commands supported by WordPerfect by dragging and dropping
      the WordPerfect application icon on top of the Script Editor icon
      (found in Apple Extras|Applescript). Page Aug 43 96 Every time I save a
      document, I find a second document gets saved along with it. This
      second document has a .bk extension at the end of the filename. What is
      happening? You are using the Original File Backup feature. This feature
      saves a second copy of each document you create. This second copy is
      saved in the same location as the original and is given a .bk filename
      extension to help you distinguish between the original and the backup
      copy. This feature is turned off by default. If you find this feature
      is turned on and you want to disable it:
      Edit|Preferences|Environment|uncheck Original File Backup. Page Aug
      44 96 I just installed version 3.5. What do I do with my old version?
      Now that 3.5 is installed, the entire folder for WordPerfect 3.x (your
      old version) can be thrown away. Make sure you don’t trash any of your
      documents. Drag them into the new WordPerfect 3.5 folder. You may want
      to save: User Dictionary (USA). This file stores any words that you
      have added to the Speller. Located in your WordPerfect 3.x
      folder|Language folder. Drag this icon into the new Language folder
      found in your new WordPerfect 3.5 folder. Stationery documents. You may
      want to save any of the stationery documents you have created or
      customized. Located in the WordPerfect 3.x folder|Stationery folder.
      Drag your stationery items into the Templates folder found in the
      WordPerfect 3.5 folder. No need to save any of the standard stationery
      files that installed with your old version of WPMac (Fax Cover Sheet,
      Memo, Business Card, etc.) These are automatically installed again with
      3.5. Only save those documents you haved made changes to or created
      from scratch. Any stationery documents you place in the 3.5 Page Aug
      45 96 Templates folder will display in the new version under the
      File|Templates menu. Styles and Macros. These automatically convert
      into 3.5 through the Library (USA) file. (See the Direct Questions
      section) Preferences. These automatically convert into 3.5 through the
      Preferences (USA) file. QuickCorrect List (USA). This file stores those
      items added to your QuickCorrect list. Located in your WordPerfect 3.1
      folder|Language folder. Drag this icon into the Language folder found
      in the WordPerfect 3.5 folder. (The QuickCorrect feature was first
      implemented in version 3.1. Thus, you will only find this QuickCorrect
      List (USA) file in the Language folder of 3.1 or 3.5.) Page Aug 46 96
      AppleScript Contest Attention AppleScript Users! Corel WordPerfect is
      putting together a new guide for the use of AppleScript with
      WordPerfect (Yes, we do listen to your requests). Now, as you well
      know, any scripting guide worth its weight in electrons needs plenty of
      good samples. That is where you come in. We are holding a contest to
      see who can come up with the best AppleScript that works with
      WordPerfect. We will award prizes to the best scripts submitted.
      Categories for judging include: Best Use of Apple Technology, Most
      Useful, and Most Humorous. Please send all submissions to:
      MacTalk@..., with the words “AppleScript Contest” in the subject
      field, and a short description of what your script does. By entering
      your script, you give Corel the consent to publish and/or share your
      creative efforts. Feel free to Page Aug 47 96 use accompanying macros
      if you wish. Just be sure to include the macro and any other extras
      that we need to run your creation. Remember, this is for a teaching
      guide, so make good use of comments and, as Thoreau said, “Simplify,
      simplify, simplify!” Why he had to say it three times, I don’t know,
      but the point is, it has to be easy enough for a budding new
      scriptophile to follow. Enter as often as you like, but please only
      submit original material of your own design. You will be notified when
      we receive your entry. Prizes will include free software and other cool
      stuff. Thanks in advance for your interest and time, Johnny Ringo Corel
      AppleScript Documancer Page Aug 48 96 WPMac Chat on CorelNet On July
      24, 1996, Ken Freeman, our Corel Product Marketing Manager for
      Macintosh participated in a live chat on CorelNet. He discussed WPMac
      and its future, as well as Corel’s commitment to the Macintosh
      platform. For those of you who missed this event, check out a copy of
      the live discussion at: http://www.corelnet.com/corelnet/discus20.htm
      Page Aug 49 96 We want to hear from you! Give us your comments and take
      the opportunity to write an article, macro, or tip and trick for the
      News. Submit all entries to: wpmacnews@.... Each entry is not
      guaranteed to be published in the News, but we will definitely work
      with you and do our best to make sure you achieve your WPMac News
      debut. WRITE FOR US AND SEE YOUR NAME IN LIGHTS Want to select a free
      CD from a stash of Corel WordPerfect CDs (selection may vary)? The only
      requirement for this free CD is to have your article published as the
      Cover Story in WPMac News. We are giving you the opportunity to write
      for us. We will select those articles that are informative,
      easy-to-read, and cover any of the features found in WordPerfect for
      the Macintosh. It’s as easy as this: • Pick a feature, or group of
      similar features, from WPMac. • Write an informative feature article.
      (Review some of the Feature Highlights from our Back Issues for helpful
      hints and guidelines). • Submit a copy of the article to:
      wpmacnews@.... Subject should be Cover Story. Please leave your
      name, address, phone, and email. Page Aug 50 96 • We will respond as
      soon as possible. No guarantees that your article will be published in
      the News (don’t worry, we will help as much as possible). • We will let
      you know if your article has been accepted as a Cover Story for the
      News and what month it will be featured. • Any questions, please send
      to: wpmacnews@... • We reserve the right to edit any part
      (content, format, etc.) of your article. LET OUR READERS SEE THOSE
      MACROS If writing is not your thing, but macros are...this is for you.
      We want to see what macros you have written to help with your work in
      WPMac. Submit any macro written in WordPerfect for Macintosh to
      wpmacnews@... (be sure you provide your name, address, phone, and
      email). Again, no guarantees that your macro will appear in the News.
      But, if we love your macro and think our readers will to, you will
      receive a free, snazzy WPMac mug. SUBMIT YOUR TIPS & TRICKS What is
      your favorite WPMac tip or trick? No free stuff given away for this
      one, but we will publish your name along side your entry in the News.
      Submit to wpmacnews@.... Include name, phone, and email. Page Aug
      51 96 GIVE US THE SCOOP What features or questions would you like to
      see covered in the News? We want to make sure that we provide you the
      best information possible. Let us know if there is anything we can
      cover in the News that will make your life and work much simpler. WE
      AIM TO PLEASE Let us know if you like the News and if you have any
      suggestions for improvement. In case it hasn’t been mentioned enough,
      send your comments to wpmacnews@....
    Your message has been successfully submitted and would be delivered to recipients shortly.