Corel Corel Draw Graphics Suite - X4 Programmming Guide
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About CorelDRAW Graphics Suite X4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About VBA in CorelDRAW Graphics Suite X4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
About Corel Corporation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 1
Understanding VBA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
What is VBA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
What is automation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Who is VBA designed for?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
How does VBA compare with other programming languages?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
What are the main elements used in VBA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
What is an object model? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
How is VBA code structured? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Declaring variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Building functions and subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Ending lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Including comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Using memory pointers and memory allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Defining scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Using Boolean comparison and assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Using logical and bitwise operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Providing message boxes and input boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Chapter 2
Getting started with macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installing VBA for CorelDRAW Graphics Suite X4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Using the Macros toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Using the Macros toolbar in CorelDRAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Using the Macros toolbar in Corel PHOTO-PAINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Using the Macro Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Using the Project Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Using the Properties window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Using the Code window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Using the toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Using the Object Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
CorelDRAW Graphics Suite X4 Programming Guide for VBA i
Chapter 3
Working with macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Creating macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Writing macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Recording macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Referencing objects in macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Referencing collections in macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Using shortcut objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Providing event handlers in macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Running macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Debugging macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Using the debugging windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Chapter 4
Creating user-interfaces for macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Creating dialog boxes for macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Coding dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Designing dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Creating toolbars and buttons for macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Creating toolbars for macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Adding captions and tooltips to macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Associating images or icons with macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Providing user interaction for macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Capturing mouse actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Capturing coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Providing documentation for macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 5
Organizing and deploying macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Organizing macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Deploying macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Deploying project files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Deploying workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Appendix
Understanding the CorelDRAW object model . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Working with documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Creating documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Opening documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Importing files into documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Switching between documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Viewing documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Changing content in documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Setting the Undo string for documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Exporting files from documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Printing documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Publishing documents to PDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Closing documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Contents ii
Working with pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Creating pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Switching between pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Reordering pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Resizing pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Deleting pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Working with layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Activating layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Locking and hiding layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Reordering layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Renaming layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Importing files into layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Deleting layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Working with shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Creating shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Selecting shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Determining shape type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Changing shape properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Coloring shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Duplicating shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Applying effects to shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Searching for shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Contents iii
Introduction
Welcome to the CorelDRAW® Graphics Suite X4 Programming Guide for VBA, your resource for using Microsoft®
Visual Basic® for Applications (VBA) to develop and distribute macro solutions in
CorelDRAW Graphics Suite X4.
About CorelDRAW Graphics Suite X4
CorelDRAW Graphics Suite X4 is an affordable and comprehensive suite of intuitive page-layout, illustration,
photo-editing, and bitmap-to-vector tracing applications. The trusted choice of professional and aspiring
designers, the suite includes new tools that fuel the creative process, simplify project management, and optimize
the graphic design workflow.
About VBA in CorelDRAW Graphics Suite X4
In 1995, Corel incorporated automation into CorelDRAW 6 by including its Corel SCRIPT™ language. This
enabled solution developers to create intelligent mini-applications within CorelDRAW, such as ones that draw
shapes, reposition and resize shapes, open and close documents, or set styles.
Corel SCRIPT was included with CorelDRAW versions 6 through 9. Although the Corel SCRIPT editor is not
included with CorelDRAW in versions 9 and later, the run-time engine is included, so scripts written for earlier
versions of CorelDRAW can easily be migrated to the latest versions.
In 1998, Corel took the strategic decision to augment the Corel SCRIPT functionality of CorelDRAW 9 by
licensing the Microsoft Visual Basic for Applications engine to handle its behind-the-scenes automation. The
addition of VBA made CorelDRAW immediately accessible to millions of VBA and Visual Basic developers
around the world.
VBA in CorelDRAW can be used as a platform for developing powerful corporate graphical solutions, such as
automated ticket generators, customized calendars, or batch-processors of files. VBA can also be used to enhance
and optimize the workflow within CorelDRAW. For example, you can improve and customize some of the builtin functionality of CorelDRAW (such as object creation, alignment, or transformation) or add page layouts onthe-fly (such as to create company letterheads).
VBA comes with a fully integrated development environment (IDE) that provides contextual pop-up lists,
syntax highlighting, line-by-line debugging, and visual designer windows. These helpful prompts and aids create
a particularly friendly learning environment for inexperienced developers.
For CorelDRAW Graphics Suite X4, VBA is available to both CorelDRAW and Corel PHOTO-PAINT®.
CorelDRAW Graphics Suite X4 Programming Guide for VBA 1
About this guide
This guide, which should be read in conjunction with the CorelDRAW and Corel PHOTO-PAINT object model
diagrams that install with CorelDRAW Graphics Suite X4, was designed as a resource for the following:
• exploring the VBA IDE and many of its advanced features
• understanding the most important CorelDRAW Graphics Suite X4 functions and how to use them
• examining how to package and deploy VBA solutions developed for CorelDRAW Graphics Suite X4
This guide should be used by anyone who is interested in automating simple and complex tasks in CorelDRAW
Graphics Suite X4 or who is developing commercial solutions that integrate with CorelDRAW Graphics Suite
X4. It is assumed that the reader already has experience with at least one other procedural programming
language, such as BASIC, Visual Basic, C, C++, Java™, Pascal, Cobol, or Fortran. This guide does not describe
the basics of procedural programming, such as functions, conditional branching, and looping. Non-programmers
should learn the basics of programming in a language such as Visual Basic or VBA before using this document to
develop CorelDRAW Graphics Suite X4 solutions.
This guide is organized into the following chapters, which deal with specific aspects of automating tasks and
building solutions in CorelDRAW Graphics Suite X4:
• Chapter 1: Understanding VBA provides a brief introduction to VBA.
• Chapter 2: Getting started with macros lets you explore the VBA workspace in CorelDRAW and Corel
PHOTO-PAINT.
• Chapter 3: Working with macros shows you how to create, run, and debug macros.
• Chapter 4: Creating user-interfaces for macros demonstrates how to provide dialog boxes, toolbars and
buttons, user interaction, and help for your macros.
• Chapter 5: Organizing and deploying macros helps you organize and deploy the macros you create.
This guide also provides an appendix (page 57), which provides detailed information on the
CorelDRAWobject model.
Finally, a glossary (page 93) defines the terms used in this guide.
Documentation conventions
The following conventions are used in this guide:
When you see This is
A note — presents information such as conditions for performing a procedure
A tip — presents information such as procedure shortcuts, variations, or benefits
In addition, this guide uses a few formatting conventions:
• User-interface items are displayed in boldface.
• Glossary items are displayed in italics.
• Information that can be substituted, such as a path or filename, is displayed in <italics and between angle
brackets>.
• Coding is formatted in a
monospace font.
Introduction 2
For more information
VBA for CorelDRAW Graphics Suite X4 also installs with the following documentation:
• VBA object model diagrams for CorelDRAW and Corel PHOTO-PAINT — These are available as Adobe®
Acrobat® Reader® (PDF) files and are installed to ..\Program Files\Corel\
CorelDRAW Graphics Suite X4\Programs.
• VBA Help files for CorelDRAW and Corel PHOTO-PAINT — These can be accessed through the Macro
Editor: select any item in the Object Browser and press F1 to access a Help topic on that item.
For comprehensive information about the features in CorelDRAW Graphics Suite X4, you can consult the user
guide, which is installed by default to ..\Program Files\Corel\CorelDRAW Graphics Suite X4\
Languages\<language>\Help\CorelDRAW Graphics Suite X4.pdf. Alternatively, you can access a Help
system from within a CorelDRAW Graphics Suite X4 application by clicking Help ` Help topics.
For the latest news, tips and tricks, and product upgrade information, you can check the CorelDRAW Graphics
Suite X4 Web site. Go to www.corel.com, and follow the links for CorelDRAW Graphics Suite X4.
For prompt and accurate information about product features, specifications, pricing, availability, services, and
technical support, contact Corel® Support Services™. For the most current information on available support and
professional services for your Corel product, please visit www.corel.com/support.
To interact with other CorelDRAW Graphics Suite users, visit www.coreldraw.com, an online community for
sharing experiences with the product, asking questions, and receiving help and suggestions from other users.
If you have any comments or suggestions about CorelDRAW Graphics Suite X4 or about the CorelDRAW
Graphics Suite X4 Programming Guide for VBA, you can submit them by using the contact information provided at
www.corel.com/contact.
About Corel Corporation
Corel is a leading developer of graphics, productivity, and digital media software, with more than 100 million
users worldwide. The company’s product portfolio includes some of the world’s most popular and widely
recognized software brands, including CorelDRAW® Graphics Suite, Corel® Paint Shop Pro®, Corel®
Painter™, Corel DESIGNER®, Corel® WordPerfect® Office, WinZip®, and iGrafx®. In 2006, Corel acquired
InterVideo, makers of WinDVD®, and Ulead, a leading developer of video, imaging, and DVD authoring
software. Designed to help people become more productive and express their creative potential, Corel’s fullfeatured software products set a higher standard for value in being easier to learn and use. The industry has
responded with hundreds of awards recognizing Corel’s leadership in software innovation, design, and value.
Corel’s products are sold in more than 75 countries through a well-established network of international resellers,
retailers, original equipment manufacturers, online providers, and Corel’s global Web sites. With its
headquarters in Ottawa, Canada, the company has major offices in the United States, the United Kingdom,
Germany, China, and Japan. Corel’s stock is traded on the NASDAQ under the symbol CREL and on the TSX
under the symbol CRE. For more information, please visit www.corel.com.
Introduction 3
Chapter 1
Understanding VBA
Before getting started with macros in CorelDRAW Graphics Suite X4, it’s important to understand a little bit
about VBA in general.
This chapter answers the following questions:
• What is VBA?
• Who is VBA designed for?
• How does VBA compare with other programming languages?
• What are the main elements used in VBA?
• How is VBA code structured?
What is VBA?
Visual Basic for Applications (more commonly known as VBA) is a built-in programming language that can
automate repetitive functions and create intelligent solutions in CorelDRAW and Corel PHOTO-PAINT.
CorelDRAW Graphics Suite X4 includes VBA version 6.4.
VBA is both a language and an editor. It is not possible to have the language without the editor, nor is it possible
to edit VBA in anything but the Macro Editor or to run VBA programs without the Macro Editor.
VBA is developed by Microsoft and is built into almost all of its desktop applications, including Microsoft®
Office. VBA is licensed by Microsoft to other companies, including Corel Corporation (in CorelDRAW Graphics
Suite, Corel DESIGNER® Technical Suite, and WordPerfect Office), Autodesk, Inc. (in AutoCAD®), and
IntelliCAD Technology Consortium (in IntelliCAD®). This makes Corel applications compatible with a wide
array of applications that support VBA.
For a complete list of applications that support VBA, consult the Microsoft Web site at
http://msdn2.microsoft.com/en-us/isv/Bb190538.aspx.
It is not necessary for an application to support VBA in order for the CorelDRAW Graphics Suite X4 VBA
engine to control that application. That means you can build solutions in CorelDRAW Graphics Suite X4 that
access databases, word processors, specialized content editors, XML documents, and more.
What is automation?
Most actions that you can do in CorelDRAW Graphics Suite X4 can be done programmatically through VBA.
This programmability of CorelDRAW Graphics Suite X4 is called automation. Automating repetitive tasks can
save time and reduce effort, while automating complex tasks can make possible the otherwise impossible.
CorelDRAW Graphics Suite X4 Programming Guide for VBA 4
In its simplest form, automation is simply recording a sequence of actions so that you can play them back time
and again. The term macro has come to include any code that is accessible to VBA while running within the
process, even though some of that code might be far more advanced than a mere set of recorded actions. For the
purposes of this guide, a macro refers to VBA functions and subroutines (which are explained in “Building functions
and subroutines” on page 10).
While it is possible to record a sequence of actions in CorelDRAW Graphics Suite X4, the real power of
automation and VBA is that these recordings can be edited to provide conditional and looping execution. For
example, a simple macro may set the selected shape’s fill color to red and apply a one-point outline; however, by
adding a condition and a looping mechanism to the VBA code, the macro could, for example, be made to seek
out each selected shape and apply only the fill to text shapes and only the outline to all other shape types.
Who is VBA designed for?
VBA can be used by both non-programmers and programmers alike.
VBA for non-programmers
VBA is based on Microsoft’s successful Visual Basic (VB) programming language. The main difference between
VBA and VB is that you cannot create stand-alone executable (EXE) files using VBA, whereas you can with VB.
That is to say, using VBA, you can create only programs that run inside the host application (in this case,
CorelDRAW or Corel PHOTO-PAINT).
VB is a “visual” version of the BASIC programming language. This means that it is a very easy language to learn,
particularly because it provides visual cues within the editor. Microsoft has added a great deal to the original
BASIC language, and it is now a powerful and fast language (although not as powerful as Java or C++, nor as
quick as C).
The aim of this guide is not to teach you how to become a programmer but instead to teach experienced
programmers how to apply their skills to developing useful solutions within CorelDRAW Graphics Suite X4. If
you are not a programmer, you may find it useful to refer to the many books that have been written about VBA
and VB before continuing to read this guide.
VBA for programmers
VBA is an in-process automation controller. In other words, it can be used to control the functionalities of
CorelDRAW Graphics Suite X4 that can be automated. In addition, because VBA runs “in-process,” it bypasses
the interprocess synchronization mechanisms so as to run much more efficiently.
All of the automation that is available to the in-process VBA is also available to external out-of-process
automation controllers, or OLE clients. This includes applications developed in programming languages that can
be used to develop OLE clients, such as the following:
• Microsoft Visual Basic, Visual C++, and Windows® Script Host
• Borland® Delphi™ and C++
• the VBA engines of other applications
Chapter 1: Understanding VBA 5
How does VBA compare with other programming languages?
VBA has many similarities with most modern, procedural programming languages, including Java and
JavaScript®, C and C++, and Windows Script Host. However, VBA runs as an in-process automation
controller, whereas the other languages (apart from JavaScript) are used to compile stand-alone applications.
VBA compared with Java and JavaScript
VBA is similar to Java and JavaScript in that it is a high-level, procedural programming language that has full
garbage collection and very little memory-pointer support. (See “Using memory pointers and memory
allocation” on page 11 for more information.) In addition, code developed in VBA — much like code developed
in Java and JavaScript — supports on-demand compilation and can be executed without being compiled.
VBA has another similarity with JavaScript in that it cannot be executed as a standalone application. JavaScript
is embedded within Web pages, as a mechanism for manipulating the Web browser’s document object model (or
“DOM”). Likewise, VBA programs are executed inside a host environment (in this case, CorelDRAW or Corel
PHOTO-PAINT) so as to manipulate the host’s object model (which is discussed in “What is an object model?” on
page 7).
Most VBA applications can be compiled to P-code so as to make them run more quickly, although the difference
is hardly noticeable given the sophistication of today’s computer hardware. Java can be similarly compiled;
JavaScript, however, cannot.
Finally, whereas VBA uses a single equals sign (
single equals sign (
=) for assignment and two equals signs (==) for Boolean comparison. (For more information on
=) for both comparison and assignment, Java and JavaScript use a
Boolean comparison and assignment in VBA, see “Using Boolean comparison and assignment” on page 12.)
VBA compared with C and C++
Visual Basic — similarly to C and C++ — uses functions. In VB, functions can be used to return a value but
subroutines cannot. In C and C++, however, functions are used regardless of whether you want to return a
value. (For more information on functions and subroutines, see “Building functions and subroutines” on
page 10.)
VBA allocates and frees memory “transparently.” In C and C++, however, the developer is responsible for most
memory management. This makes using strings in VBA even simpler than using the
Finally, whereas VBA uses a single equals sign (
equals sign (
=) for assignment and two equals signs (==) for Boolean comparison. (For more information on
=) for both comparison and assignment, C and C++ use a single
CString class in C++.
Boolean comparison and assignment in VBA, see “Using Boolean comparison and assignment” on page 12.)
VBA compared with Windows Script Host
Windows Script Host (WSH) is a useful addition to Windows for doing occasional scripting and automation of
Windows tasks. WSH is an out-of-process automation controller that can be used to control CorelDRAW
Graphics Suite X4. However, because WSH scripts cannot be compiled (and must be interpreted as they are
executed) and must be run out of process, they tend to be slow.
WSH is a host for a number of scripting languages, each of which has its own syntax. However, the standard
language used by WSH is a macro language resembling Visual Basic, so for standard scripts, the syntax is the
same as in VBA.
Chapter 1: Understanding VBA 6
What are the main elements used in VBA?
If you’ve ever developed object-oriented code in C++, Borland Delphi, or Java, you’re already familiar with the
concepts of “classes,” “objects,” “properties,” and “methods,” but let’s re-examine them in greater detail as they
apply to VBA.
A class is a description of something. For example, the class “car” is a small vehicle with an engine and four
wheels.
An object is an instance of a class. If we extend the car metaphor, then the actual, physical car that you go out and
purchase for the purposes of driving is an object (that is, an instance of the class “car”). In the context of
CorelDRAW, each open document is an instance of the
instance of the
Page class, and each layer (and each shape on each layer) are more instances of more classes.
Most classes have properties. For example, the properties of the class “car” are that it is small, it has an engine, and
it has four wheels. Every instance of the class “car” (that is, every object in that class) also has properties such as
color, speed, and number of seats. Some properties, called “read-only” properties, are fixed by the design of the
class; for example, the number of wheels or seats does not (usually) vary from car to car. However, other
properties can be changed after the object has been created; for example, the speed of the car can go up and
down, and, with a bit of help, its color can be changed. In the context of CorelDRAW,
name, a resolution, and horizontal and vertical ruler units; individual shapes have outline and fill properties, as
well as a position and a rotation factor; and text objects have text properties, which may include the text itself.
A method is an operation that the object can have performed on itself. In the example of the class “car,” the car can
be made to go faster and slower, so two methods for the class are “accelerate” and “decelerate.” In the context of
CorelDRAW, documents have methods for creating new pages, layers have methods for creating new shapes,
and shapes have methods for applying transformations and effects.
Document class, each page in the document is an
Document objects have a
Objects are often made up of other smaller objects. For example, a car contains four objects of the class “wheel,”
two objects of the class “headlight,” and so on. Each of these child objects has the same properties and methods
of its class-type. In the context of CorelDRAW, a document object contains page objects, which contain layer
objects, which contain shape objects, some of which contain other objects. This parent/child relationship of
objects is an important one to recognize, particularly when referencing an individual object.
Some classes “inherit” features from their parents. For example, in the context of CorelDRAW, the
has many subtypes (or “inherited types”), including
subtypes can make use of the basic members of the
Rectangle, Ellipse, Curve, and Text. All of these
Shape type, including methods for moving and transforming
Shape type
the shape and for setting its color. However, the subtypes also have their own specialist members; for example, a
Rectangle can have corner radii, whereas Text has an associated Font property.
What is an object model?
VBA relies on an application’s object model for communicating with that application and modifying its documents.
Without an object model, VBA cannot query or change an application’s documents.
Object models in software provide a high level of structure to the relationship between parent and child objects.
They also allow object types or classes to be used repeatedly in different ways; for example, a
be of the type “group” and may contain other
Shape objects, some of which may also be of the type “group,” or
Shape object may
Chapter 1: Understanding VBA 7
“rectangle,” or “curve,” or “text.” This high level of organization and re-use makes the object model simple to use
and yet powerful — and also easy to navigate by using the VBA Object Browser (which is discussed in “Using
the Object Browser” on page 23).
Remember, though, that the object model is the map that the VBA language uses to access the various members
— objects, methods, and properties — of a document, and to make changes to those members. Without the
object model, it is simply impossible to gain access to the objects in the document.
Understanding object hierarchy
In any object model, each object is a child of another object, which is a child of another object. Also, each object
has child members of its own — properties, objects, and methods. All of this comprises an object hierarchy that
is the object model. In CorelDRAW, the root object of all objects is the
Application object, because all objects
are children or grandchildren of the application.
In order to “drill down” through the layers of hierarchy to get to the object or member that you want, you must
use a standard notation. In VBA, as in many object-oriented languages, the notation is to use a period (
. ) to
indicate that the object on the right is a member (or child) of the object on the left.
Application.Documents(1).Pages(1).Layers(1).Shapes(1).Name = "Bob"
It is not usually necessary to use the full hierarchical (or fully qualified) reference to an object or its properties.
Some of the object-syntax in the fully qualified reference is mandatory or required; however, other syntax is
optional (because a shortcut object for it is available, or because it is implicit or implied), and so it can either be
included for clarity or omitted for brevity.
A shortcut object is merely a syntactical replacement for the long-hand version of the object. For example, the
shortcut object
Application.ActiveDocument.ActivePage.ActiveLayer, while the object shortcut ActiveSelection
replaces the long-hand version
ActiveLayer replaces the long-hand version
Application.ActiveDocument.Selection. For information on the shortcut
objects that are available to CorelDRAW, see “Using shortcut objects” on page 33.
For detailed information on the CorelDRAW object model, see the Appendix.
How is VBA code structured?
Because VBA is a procedural language that shares much in common with all procedural languages, your current
knowledge should help you get off to a quick start with VBA.
This section examines the following topics on VBA structure and syntax:
• Declaring variables
• Building functions and subroutines
• Ending lines
•Including comments
• Using memory pointers and memory allocation
•Defining scope
• Using Boolean comparison and assignment
• Using logical and bitwise operators
• Providing message boxes and input boxes
Chapter 1: Understanding VBA 8
The Macro Editor formats all of the code for you (as discussed in “Formatting code automatically” on
page 20). The only custom formatting that you can do is to change the size of the indentations.
VBA can create object-oriented classes, although these are a feature of the language and are not discussed
in detail in this guide.
Declaring variables
In VBA, the construction for declaring variables is as follows:
Dim foobar As Integer
The built-in data types are Byte, Boolean, Integer, Long, Single, Double, String, Variant, and several
other less-used types including
Variables can be declared anywhere within the body of a function, or at the top of the current module. However,
it is generally a good practice to declare a variable before it is used; otherwise, the compiler interprets it as a
Variant, and inefficiencies can be incurred at run time.
Date, Decimal, and Object.
Booleans take
Long results in True being converted to a value of –1.
a
False to be zero and True to be any other value, although converting from a Boolean to
To get more information about one of the built-in data types, type it into the code window, select it, and
then press F1.
Data structures can be built by using the following syntax:
Public Type fooType
item1 As Integer
item2 As String
End Type
Dim myTypedItem As fooType
The items within a variable declared as type fooType are accessed using dot notation:
myTypedItem.item1 = 5
Declaring strings
Strings in VBA are much simpler than in C. In VBA, strings can be added together, truncated, searched forwards
and backwards, and passed as simple arguments to functions.
To add two strings together, simply use the concatenation operator (
Dim string1 As String, string2 As String
string2 = string1 & " more text" + " even more text"
&) or the addition operator (+):
In VBA, there are many functions for manipulating strings, including InStr(), Left(), Mid(), Right(),
Len(), and Trim().
Chapter 1: Understanding VBA 9
Declaring enumerated types
To declare an enumerated type, use the following construction:
Public Enum fooEnum
ItemOne
ItemTwo
ItemThree
End Enum
The first item in an enumerated type is assigned, by default, a value of zero.
Declaring arrays
To declare an array, use parentheses — that is, the ( and ) symbols:
Dim barArray (4) As Integer
The value defines the index of the last item in the array. Because array indexes are zero-based by default, there
are five elements in the preceding sample array (that is, elements
0 thru 4, inclusive).
Arrays can be resized by using
ReDim. For example, the following code adds an extra element to barArray, but
preserves the existing contents of the original five elements:
ReDim Preserve barArray (6)
Upper and lower bounds for an array can be determined at run time with the functions UBound() and
LBound().
Multidimensional arrays can be declared by separating the dimension indexes with commas:
Dim barArray (4, 3)
Building functions and subroutines
VBA uses both functions and subroutines (or “subs”). Functions can be used to return a value, whereas subs cannot.
In VBA, functions and subs do not need to be declared before they are used, nor before they are defined. In fact,
functions and subs need to be declared only if they actually exist in external system dynamic-linked libraries
(DLLs).
Typical functions in a language such as Java or C++ can be structured as follows:
void foo( string stringItem ) {
// The body of the function goes here
}
double bar( int numItem ) { return 23.2; }
In VBA, however, functions are structured as in the following example:
Chapter 1: Understanding VBA 10
Public Sub foo (stringItem As String)
' The body of the subroutine goes here
End Sub
Public Function bar (numItem As Integer) As Double bar = 23.2
End Function
To force a function or sub to exit immediately, you can use Exit Function or Exit Sub (respectively).
Ending lines
In VBA, each statement must exist on its own line, but no special character is required to denote the end of each
line. (This is in contrast to the many programming languages that use the semicolon to separate individual
statements.)
To break a long VBA statement over two or more lines, each of the lines (other than the last line) must end with
an underscore (
newString = fooFunction ("This is a string", _
5, 10, 2)
It is also possible to combine several statements in a single line by separating them with colons:
a = 1 : b = 2 : c = a + b
_ ) preceded by at least one space:
A line cannot end with a colon. Lines that end with a colon are labels used by the Goto statement.
Including comments
Comments in VBA — similarly to in ANSI, C++, and Java — can be created only at the end of a line.
Comments begin with an apostrophe (
' ) and terminate at the end of the line.
Each line of a multi-line comment must begin with its own apostrophe:
a = b ' This is a really interesting piece of code that
' needs so much explanation that I have had to break
' the comment over multiple lines.
To comment out large sections of code, use the following code (similarly to in C or C++):
#If 0 Then ' That's a zero, not the letter 'oh'.
' All this code will be ignored by
' the compiler at run time!
#End If
Using memory pointers and memory allocation
VBA does not support C-style memory pointers. Memory allocation and garbage collection are automatic and
transparent, just as in Java and JavaScript (and some C++ code).
Chapter 1: Understanding VBA 11
Passing values “by reference” and “by value”
Most languages, including C++ and Java, pass an argument to a procedure as a copy of the original. If the
original must be passed, then one of two things can happen:
• a memory pointer is passed that directs to the original in memory
• a reference to the original is passed
The same is true in VB, except that passing a copy of the original is called passing by value and passing a reference
to the original is called passing by reference.
By default, function and subroutine parameters are passed by reference. This means that a reference to the
original variable is passed in the procedure’s argument, and so changing that argument’s value within the
procedure, in effect, changes the original variable’s value as well. This is a great way of returning more than one
value from a function or sub. To explicitly annotate the code to indicate that an argument is being passed by
reference, you can prefix the argument with
ByRef.
If you want to prevent the procedure from changing the value of the original variable, you can force the copying
of an argument. To do this, prefix the argument with
ByVal functionality is similar to the ability of C and C++ to pass a copy of a variable, or to pass a pointer to the
ByVal, as shown in the example that follows. This ByRef/
original variable.
Private Sub fooFunc (ByVal int1 As Integer, _
ByRef long1 As Long, _
long2 As Long) ' Passed ByRef by default
In the preceding example, arguments long1 and long2 are both, by default, passed by reference. Modifying
either argument within the body of the function modifies the original variable; however, modifying
int1 does
not modify the original because it is a copy of the original.
Defining scope
Yo u c an d ef in e t he scope of a data type or procedure (or even an object). Data types, functions, and subs (and
members of classes) that are declared as private are visible only within that module (or file), while functions that
are declared as public are visible throughout all the modules; however, you may have to use fully qualified
referencing if the modules are almost out of scope — for example, if you are referencing a function in a different
project.
Unlike C, VBA does not use braces — that is, the
is defined by an opening function or sub definition statement (that is,
statement (that is,
End Function or End Sub). Any variables declared within the function are available only
{ and } symbols — to define local scope. Local scope in VBA
Function or Sub) and a matching End
within the scope of the function itself.
Using Boolean comparison and assignment
In VB, Boolean comparison and assignment are both performed by using a single equals sign (=):
If a = b Then c = d
This is in contrast to many other languages that use a double equals sign for a Boolean comparison and a single
equals sign for assignment:
Chapter 1: Understanding VBA 12
if( a == b ) c = d;
The following code, which is valid in C, C++, Java, and JavaScript, is invalid in VBA:
if( ( result = fooBar( ) ) == true )
This would have to be written in VBA as the following:
result = fooBar( )
If result = True Then
For other Boolean comparisons, VBA uses the same operators as other languages (except for the operators for “is
equal to” and “is not equal to”). All the Boolean-comparison operators are provided in the following table:
Comparison VBA operator C-style operator
Is equal to
Is not equal to
Is greater than
Is less than
Is greater than or equal to
Is less than or equal to
The result of using one of the Boolean operators is always either
===
<> !=
>>
<<
>= >=
<= <=
True or False.
Using logical and bitwise operators
In VBA, logical operations are performed by using the keywords And, Not, Or, Xor, Imp, and Eqv, which perform
the logical operations AND, NOT, OR, Exclusive-OR, logical implication, and logical equivalence (respectively).
These operators also perform Boolean comparisons.
The following code shows a comparison written in C or a similar language:
if( ( a && b ) || ( c && d ) )
This would be written as follows in VBA:
If ( a And b ) Or ( c And d ) Then
Alternatively, the above could be written in the following full long-hand form:
If ( a And b = True ) Or ( c And d = True ) = True Then
The following table provides a comparison of the four common VBA logical and bitwise operators, and the Cstyle logical and bitwise operators used by C, C++, Java, and JavaScript:
VBA operator C-style bitwise operator C-style Boolean operator
And & &&
Not ~ !
Or | ||
Chapter 1: Understanding VBA 13
VBA operator C-style bitwise operator C-style Boolean operator
Xor ^
Providing message boxes and input boxes
You can present simple messages to the user by using the MsgBox function:
Dim retval As Long
retval = MsgBox("Click OK if you agree.", _
vbOKCancel, "Easy Message")
If retval = vbOK Then
MsgBox "You clicked OK.", vbOK, "Affirmative"
End If
You can also get strings from the user by using InputBox function:
Dim inText As String
inText = InputBox("Input some text:", "type here")
If Len(inText) > 0 Then
MsgBox "You typed the following: " & inText & "."
End If
If the user clicks Cancel, the length of the string returned in inText is zero.
Chapter 1: Understanding VBA 14
Chapter 2
Getting started with macros
Now that you understand a bit about VBA, you’re ready to get started with macros.
This chapter covers the following topics:
• Installing VBA for CorelDRAW Graphics Suite X4
• Using the Macros toolbars
•Using the Macro Editor
Installing VBA for CorelDRAW Graphics Suite X4
Before you can develop and run macros in CorelDRAW Graphics Suite X4, you may need to install the VBA
feature.
When you perform a “typical installation” of CorelDRAW Graphics Suite X4, VBA is installed by
default.
To install VBA
1 Insert CorelDRAW Graphics Suite X4 Disc 1 into the CD drive.
If the installation wizard does not start automatically, click Start ` Run on the Windows taskbar, and then
type X:\CGS14\Setup.exe (where X is the letter that corresponds to the CD drive).
2 Follow the on-screen instructions.
3 When you are prompted to click Install Now to install the default settings, click the Features tab.
The Features page lets you customize your installation.
4 In the Utilities list box, enable the Visual Basic for Applications 6.4 checkbox.
CorelDRAW Graphics Suite X4 Programming Guide for VBA 15
In the Utilities list box, enable the Visual Basic for Applications 6.4 checkbox
Using the Macros toolbars
CorelDRAW and Corel PHOTO-PAINT feature a Macros toolbar that lets you access common macro
functionalities.
Using the Macros toolbar in CorelDRAW
CorelDRAW has a toolbar that provides easy access to several macro features and to the Macro Editor.
The Macros toolbar in CorelDRAW
The toolbar buttons provide the following functions:
• running macros
•opening the Macro Editor
• switching the Macro Editor between its modes for designing and running macros
• recording macros
• pausing the recording of macros
• stopping the recording of macros
To display the Macros toolbar in CorelDRAW
• Click Window ` To o l b a r s ` Macros.
A check mark next to the command indicates that the toolbar is displayed.
Using the Macros toolbar in Corel PHOTO-PAINT
Corel PHOTO-PAINT has a toolbar that provides easy access to the Macro Editor.
Chapter 2: Getting started with macros 16
The Macros toolbar in Corel PHOTO-PAINT
The toolbar buttons provide the following functions:
• running macros
•opening the Macro Editor
• switching the Macro Editor between its modes for designing and running macros
To display the Macros toolbar in Corel PHOTO-PAINT
• Click Window ` To o l b a r s ` Macro Editor.
A check mark next to the command indicates that the toolbar is displayed.
Using the Macro Editor
The Macro Editor that is included with VBA is similar to the one included with full Visual Basic.
The Macro Editor (formerly called the VB Editor) lets you develop code and dialog boxes, browse the object tree
and the modules within each project, set individual properties for objects, and debug code. However, it’s
important to note that the Macro Editor for VBA cannot compile executable (EXE) program files.
The Macro Editor features several windows and toolbars, all of which are discussed in this section. The three
available windows are the Project Explorer (see page 18), the Properties window (see page 19), and the Code
window (see page 19). The four available toolbars (see page 22), are the Standard toolbar, the Debug toolbar,
the Edit toolbar, and the UserForm toolbar, of which you will use the Standard and Debug toolbars most
often.
Standard
toolbar
Debug
toolbar
Project
Explorer
Code
window
Properties
window
Edit
toolbar
UserForm
toolbar
The Macro Editor
Chapter 2: Getting started with macros 17
The Macro Editor also lets you access the Object Browser (see page 23).
You can invoke the Macro Editor from within CorelDRAW or Corel PHOTO-PAINT. Although this starts VBA
as a new application in Windows, it runs within the CorelDRAW or Corel PHOTO-PAINT process.
To start the Macro Editor
• Click To o l s ` Macros ` Macro Editor, or press Alt + F11.
To switch between the Macro Editor and CorelDRAW or Corel PHOTO-PAINT, use the Windows
taskbar, or press Alt + F11 or Alt + Tab.
Using the Project Explorer
The Project Explorer is essential for navigating macro projects and their constituent documents/objects, forms,
modules, and class modules.
The Project Explorer with a module selected
Each type of item in the Project Explorer has an icon assigned to it:
Icon Meaning
project
folder
document/object
form
module
Chapter 2: Getting started with macros 18
Icon Meaning
class module
To display or hide the Project Explorer
• Click View ` Project Explorer, or press Ctrl + R.
Using the Properties window
The Properties window lists all of the editable properties for the currently selected object. Many macro objects
— including projects, modules, and forms and their controls — have property sheets that can be modified.
The Properties window, showing the properties of a form
The Properties window is automatically updated when you select an object, or when you change the properties
of the selected object by using other methods (for example, by using the mouse to move and resize form
controls).
To display or hide the Properties window
• Click View ` Properties window, or press F4.
Using the Code window
The Code window is where you spend most of your time when working on macros. A standard code editor in the
style of Microsoft® Visual Studio®, the Code window lets you format code automatically, color and check
syntax automatically, jump to definitions, and use contextual pop-up lists and automatic completion.
If you are already familiar with any of the Microsoft Visual Studio editors, the Macro Editor’s Code window will
be entirely familiar to you.
Chapter 2: Getting started with macros 19
The Code window
Formatting code automatically
The Macro Editor formats code automatically for you — even the capitalization of keywords, functions,
subroutines, and variables is taken care of by the MacroEditor, irrespective of what you type.
You cannot custom-format code, although you can set the indentation for each line, as well as the placing of
custom line breaks.
When it comes to calling functions and subs, you must adhere to the following rules:
• If you are calling a function and you are using the returned value, the parentheses around the parameters are
mandatory (just as in most modern programming languages):
a = fooFunc (b, c)
• However, if the returned value from a function call is being discarded, or if you are calling a sub, the
parentheses must be left out (unlike in most other languages):
barFunc d, e
fooBarSub f
• If you prefer always to see the parentheses, use the Call keyword before the function or sub call:
Call barFunc (d, e)
Call fooBarSub (f)
Coloring syntax automatically
When you develop code in the Code window, the editor colorizes each word according to its classification:
•VBA keywords and programming statements are usually displayed in blue.
• Comments are displayed in green.
• All other text is displayed in black.
This colorization makes the code much easier to read.
Chapter 2: Getting started with macros 20
Syntax highlighting and coloring
The Code window also uses the following colorization techniques:
• Lines of code containing errors are displayed in red.
• Selected text is white on blue.
• The line where execution paused for debugging is shown as a yellow highlight.
• Breakpoints that you set for debugging purposes are shown as a red dot in the left margin with the code in
white on a red background.
• Bookmarks (which you set in the code) are indicated by a blue dot in the left margin.
Breakpoints (along with bookmarks) are lost when you quit the application. For more information on
them, see “Setting breakpoints” on page 37.
You can modify the default colors for syntax highlighting by clicking Tools ` Options, clicking the
Editor format tab, and making your changes.
Checking syntax automatically
Every time you move the cursor out of a line of code, the editor checks the syntax of the code in that line; if it
finds an error, it changes the color of the text of that line to red and displays a pop-up a warning. This real-time
checking is useful (particularly when you are learning to program macros) because it indicates many possible
errors in the code without having you run the code.
You can disable pop-up warnings by clicking Tools ` Options, clicking the Editor tab, and then
disabling the Auto syntax check check box. The Macro Editor still checks the syntax and highlights
erroneous lines in red, but it stops displaying a warning when you paste text from another line of code.
Jumping to definitions
You can jump directly to the definition of a variable, procedure, or object by right-clicking the item in the Code
window and then clicking Definition. This takes you either to the definition of the variable or function in the
code or to the object’s definition in the Object Browser.
To return to where you requested the definition, right-click, and then click Last position in the Code
window.
Chapter 2: Getting started with macros 21
Using contextual pop-up lists and automatic completion
As you write procedures and define variables, the Macro Editor adds these items to an internal list that already
contains all of its built-in keywords and enumerated values. As you type, the Macro Editor presents you with a
list of candidate words that you may want to insert at the current position; this list is contextual, so the Macro
Editor usually presents only the words that are valid for the current position.
Auto-completion pop-up menu
This list makes code development quicker and more convenient, particularly because you do not need to
remember every function and variable name but can instead choose them from the list provided. If you type the
first few characters of the word you want to use, the list advances to the nearest candidate that matches the
characters you’ve entered. Select the word you want to use, and either type the character that you want to have
follow the word (typically a space, line feed, parenthesis, period, or comma) or press Ta b or Ctrl + Enter to
enter only the word.
To force the pop-up menu display, you can press Ctrl + Spacebar. The menu scrolls to the word that
most closely matches the characters that you have typed so far. This technique is also useful for filling
parameter lists when calling a function or subroutine. If there is only one exact match, the Macro Editor
inserts the word without popping up the list. To display the pop-up list for the selected keyword at any
time without auto-filling it, press Ctrl + J.
Using the toolbars
The Macro Editor features four toolbars that you can use to carry out your VBA tasks.
The Standard toolbar is the default toolbar.
The Standard toolbar
The Debug toolbar contains buttons for common debugging tasks (as discussed in “Debugging macros” on
page 36).
The Debug toolbar
Chapter 2: Getting started with macros 22
The Edit toolbar contains buttons for common editing tasks.
The Edit toolbar
The UserForm toolbar contains buttons specific to designing forms (as discussed in “Designing dialog boxes” on
page 44).
The UserForm toolbar
You can choose to display or hide each toolbar.
To display or hide a toolbar
• Click View ` To o l b a r s , and then click the command that corresponds to the toolbar you want to display or
hide.
A check mark next to a command indicates that its toolbar is currently displayed.
You can “float” a toolbar by dragging it from the menu bar.
You can dock a toolbar by dragging it to the menu bar.
Using the Object Browser
The Object Browser is one of the most useful tools provided by the Macro Editor. The Object Browser displays
the entire object model of all referenced components (that is, all ActiveX® or OLE objects that are used by the
project) and, most importantly, the object model of CorelDRAW or Corel PHOTO-PAINT — all in an easy-touse, structured format.
Project/Library
list box
search controls
Search Results
window
Class list
Member list
Information
window
The Object Browser window
Help button
View definition
button
Copy to
Clipboard
button
navigation
buttons
Chapter 2: Getting started with macros 23
To open the Object Browser, click View ` Object Browser, or press F2.
To reference the object models for other applications, click Tools ` References. Referenced components
can be accessed by the VBA code.
All of the referenced objects — plus the current module — are listed in the Project/Library list box in the
upper-left corner of the Object Browser. By default, all of the member classes for the referenced objects are
provided in the Class list.
It is easier to use the Object Browser when only one project or library is displayed. To display only one
project or library, choose it from the Project/Library list box.
More detailed information follows about certain Object Browser elements.
Using the Class list
The Class list shows all of the classes in the current project or library.
When you select a class in the Class list, the members of that class are shown in the Member list.
Every project or library has an object model that contains a number of member classes. Next to each item in the
Class list, an icon depicts its class type:
Class icon Type
global value
module
enumerated type
type
class module
Global values (which apply to the selected project in its entirety) include individual members from enumerated types
(such as text paragraph alignments, shape types, and import/export filters).
Member classes of an object have their own members.
To receive detailed information about a selected item, click the Help button at the top of the Object
Browser.
Using the Member list
The Member list shows all of the properties, methods, and events that are members of the current class. Each
member is given an icon according to its type:
Chapter 2: Getting started with macros 24
Class icon Type
property
implied or default property
method
event
constant
Property members may be simple types (such as Booleans, integers, or strings), or they may be a class or
enumerated type from the Class list. A property that is based on a class from the Class list inherits all the
members of that class.
Many classes have a default property, indicated by a blue dot in their icon. The default property is implied if no
property name is given when getting or setting the value of the parent object. For example, collection types have
the default property
Item, which can be indexed. However, because Item is usually the default property, in such
instances, it is not necessary to specify the item property. Here,
ActiveSelection.Shapes.Item(1).Selected = False
is the same as the shorter
ActiveSelection.Shapes(1).Selected = False
because Item is the default or implied property of a collection of shapes.
Methods are commonly known as “member functions” — functions that the class can perform on itself. A good
example is the
vector. The following code moves the selected shapes
Move method of the Shape class, which is used to move a CorelDRAW shape using an [x, y]
2 measurement units to the right and 3 measurement units
upwards:
ActiveSelection.Move 2, 3
If the return value of a function is not used, the function call does not take parentheses around the argument list
unless the
Call keyword is used.
For more information about
ActiveSelection, see the Appendix.
Some classes have various events associated with them. By setting up an event handler for a class’s event, when that
event occurs in the application, the event’s handler is called. This functionality enables sophisticated applications
to be developed that respond automatically to what is happening within the application.
Commonly handled events include the
PageActivate, and SelectionChange events of the Document class.
BeforeClose, BeforePrint, BeforeSave, ShapeMove,
Chapter 2: Getting started with macros 25
Only the Document, GlobalMacroStorage, and AddinHook classes have events in CorelDRAW. The
AddinHook class is not discussed in this guide.
The constants listed in the Member list are either members of enumerated types or defined as
Public in a
module. Enumerated types are used to group related items from a closed list, such as CorelDRAW shape types,
import/export filters, and alignments. These constants can be used anywhere an integer value is required.
Most CorelDRAW constants begin with
cdrOutlineBevelLineJoin, cdrCurveShape, and cdrSymmetricalNode). Some constants begin with prn
pdf. Visual Basic also has its own constants, including ones for keystrokes (such as vbKeyEnter) and dialog
or
box buttons (such as
vbOK).
cdr (for example, cdrLeftAlignment, cdrEPS,
To receive detailed information about a selected item, click the Help button at the top of the Object
Browser.
Using the Information window
The Information window gives information about the selected class or class member. This information includes
a “prototype” of the member, its parent, and a short description of the member, and it also states whether the
member is a read-only property.
The Information window
The types of any function parameters and properties are given as hyperlinks to the type definition or class itself,
if the type is defined within the current object model. For example, the
figure is a member of the
PHOTOPAINT class, so to view the class and its members, you can click the Application hyperlink.
it is a
PHOTOPAINT Document class; however, Application is also the property’s type, and
Application property in the preceding
To increase the height of the Information window, drag the top border of the window upwards to reveal
its contents, or scroll down using the scrolls bar at the right of the window.
Using the search controls
You can search the object model for a matching string. This is useful for finding a class or member whose name
you can only partly remember, or for finding classes and members that have similar names (such as names based
on, or containing, the word “open”).
Chapter 2: Getting started with macros 26
Loading...