Presentation on theme: "Automating with Macros Today we are going to at how to automate frequently used processes with macros: What is a macro? What do we want to automate? How."— Presentation transcript:
Automating with Macros Today we are going to at how to automate frequently used processes with macros: What is a macro? What do we want to automate? How do we create the macro? What is a user interface?
What is a Macro? A macro is a small program that can be used to automate a frequently-repeated process. In Microsoft Office applications, they are: recorded, written from scratch (because it’s something you can’t record), or recorded & edited created using a program language called Visual BASIC for Applications (VBA) triggered using shortcut keys or buttons attached to different events – e.g. opening or closing things, or changing sheets in Excel
Why Use a Macro? As macros contain a series of steps that can be triggered by a single event, they are used if: you regularly want to do a task that involves lots of steps – key presses, mouse clicks, etc. you want to perform a task when something happens… –e.g. you always want to start on Sheet 1 when someone opens your spreadsheet file –e.g. to display a message to remind someone to do something at a certain time or when a certain value is changed …to improve the user interface
What is a User Interface? the user is the person who is using the computer the user interface (or the human/computer interface) is what the user sees, and includes: the physical controls – buttons, etc. what the system looks like how the system accepts input from the user how the system responds to user input how the system outputs the results of processing
What Makes a Good User Interface? Good user interfaces are: Safe – not ambiguous or confusing (especially in safety critical applications) Effective – they do what they’re supposed to do, and quickly Efficient – they are clear and easy to use User-friendly – intuitive and easy to learn Enjoyable – they can be irritating, e.g. “Are you sure?” messages with no Yes or No buttons
Designing the User Interface When designing the user interface, what will you consider? Who will be using the system: What is their level of skill and knowledge? Are there any special physical requirements? Will there be a range of users? What does the system actually do? How many options are there, and how accessible do they need to be? The environment in which it will be used – e.g. military use, temperature, noise, motion, moisture The technology available – iris recognition, voice, etc.