EWSTM8 Series Tutorial 03_ Overview of the Main Window and Toolbar

Publisher:zhaodawei617Latest update time:2021-03-01 Source: eefocus Reading articles on mobile phones Scan QR code
Read articles on your mobile phone anytime, anywhere

1Written in front

In order to make it easier for beginners to master the relevant knowledge of the IAR tool, I will start with an overall overview and then move on to specific details.


This article first gives an overview of the default main window interface, gives a general understanding of the IAR integrated development environment, and then gives an overview of one of the commonly used toolbars.


This article mainly summarizes the following two parts:

1. Main Window


2. Toolbar

Main Toolbar Overview

Debug Toolbar Overview

Toolbar options configuration


  In order to make it convenient for everyone to view the tutorial anytime and anywhere on their mobile phones while taking the bus, subway, or going out to do business, this article is included in the [EWSTM8 Series Tutorial]. You can view it by replying [EWSTM8 Series Tutorial] on the WeChat public account.


2

Main window

In order to give everyone a general understanding of the IAR integrated development environment, here is an overview of the meaning of each window in the main interface (IAR default editing state).


Note: There are some differences between IAR windows in edit mode and debug mode. This chapter mainly provides a brief overview based on [Edit Mode]. The detailed content and windows in debug mode will be gradually described in the following textbooks of this series.


When you open an IAR project, a main window interface similar to the one shown below will generally appear, which mainly includes 6 windows, as shown below:

Menu Bar: Menu Bar

I believe everyone is familiar with this window. Any regular software has a window column such as File, Edit, View, Help, etc. This is the menu bar window.


This window is a relatively important window of IAR, which contains almost all the operations of IAR. There are some differences between the edit mode and the debug mode, which will be described later.


Tool Bar: Toolbar

This window contains some common shortcut buttons, which will be described below in this article.


Workspace Window: Workspace Window

A workspace can contain multiple projects. This window mainly displays the contents of the project items under the workspace (projects, groups, source code files, etc.). As shown in the above figure, the window contains multiple projects (Project1, Project2...), and you can pay attention to the following article about creating multiple projects.


Edit Window: Edit Window

This window needs no further explanation, it is the window where we usually edit code.


Message Window: Information Window

This window includes windows for compilation information, debugging information, search information, etc.


Status Bar: Status Bar

This window contains some status information such as ready status, number of error warnings, cursor row, character encoding, keyboard Num lock, etc.


3 Toolbar

IAR Tool Bar has two types: Main Tool Bar and Debug Tool Bar. In the edit (default) state, only the Main Tool Bar is displayed. After entering the debug mode, the Debug Tool Bar will be added, as shown below:

picture


3.1 Main Toolbar

In the edit (default) state, there is only the main toolbar, which contains the shortcut buttons commonly used in the edit state. Of course, the functions of these buttons can basically be achieved through shortcut keys.

picture

New Document Ctrl + N

OpenOpen fileCtrl + O

Save Save the file Ctrl + S

Save AllSave all files

PrintPrint fileCtrl + P

Cut Ctrl + X

CopyCtrl + C

Paste Ctrl + V

Undo Edit Ctrl + Z

Redo Resume editing Ctrl + Y

Quick Search Text Box Quick Search Text Box

Find Previous Search forward Shift + F3

Find Next Search backward F3

Find (Enhanced) Ctrl + F

Replace Ctrl + H

Go to row Ctrl + G

Toggle Bookmark Mark/Unmark Bookmark Ctrl + F2

Previous Bookmark Jump to the previous bookmark Shift + F2

Next Bookmark Jump to the next bookmark F2

Navigate Backward Jump to the previous step Alt + Left Arrow

Navigate Forward Jump to the next step Alt + right arrow

Compile Compile the current (file, group) Ctrl + F7

Make compile project (build) F7

Stop Build Stop compiling Ctrl + Break

Toggle BreakpointEdit/Cancel breakpoint Ctrl + F9

Download and Debug Download and debug Ctrl + D

Debug without Downloading

Toolbar Options (focused on in Section 3.3 below)


The above is just a brief description of the basic meaning of each shortcut button. The following will explain in detail the specific meanings of some commonly used buttons.


A. Bookmarks

Bookmarks are very useful when compiling, as they allow you to quickly find the line where the bookmark is located. You can use shortcut buttons, but it is usually recommended to use shortcut keys (F2, Ctrl + F2, Shift + F2).


Bookmark animation effect:


B. Jump to previous/next step

Jumps are the "footsteps" left by tracing the code when compiling the code. We can find these "footsteps" in this way, and we can also operate them through shortcut keys.


Jump to previous/next step animation effect:


C. Download and debug

Many people ask what is the difference between the two buttons "Download and Debug" and "Debug without Downloading"?

Answer: Download and Debug: Debug after downloading the code.

Debug without Downloading: Only debug without downloading. That is to say, if you have downloaded the code before, you only need to click this button again, otherwise an error will occur.


The two button icons are slightly different in edit and debug mode. In debug mode, you can download/debug again.


3.2 Debug Toolbar

The debug toolbar has a row of shortcut buttons that appear only in debugging mode. These buttons are not available in editing mode.


When you click the debug button and enter the debug state, a Debug menu will be added to the menu bar (the content is similar to the debug toolbar). Similarly, a debug toolbar will be added to the toolbar, as shown below:


From left to right:

Step Over Run line by line F10

Step Into Jump into running F11

Step Out Jump out of the run Shift + F11

Next Statement runs to the next statement

Run to CursorRun to the cursor line

Go full speed F5

BreakStop running

Reset


Running line by line is also called step-by-step running, jumping into running is also called single-step running, and running to the next statement is similar to running line by line.


3.3 Toolbar options configuration

This section mainly teaches you how to customize toolbar (icon) buttons. If we don't want some buttons in the toolbar (such as: copy, paste), or we want to add a tool button, how to achieve it?


A. Enter the custom toolbar

picture


B. Delete the toolbar

To delete the Copy button: press and hold the Copy button -> drag it out of the toolbar.

picture


Delete button animation effect:

picture


C. Add tool button

For example: to add a tool configuration button, find the [Tool Configuration] button in the command, press and hold -> drag it to the toolbar (to the position you want).


Add button animation effects:


D. Add display text label

Display text labels, that is, display the meaning of the icon button below the icon, so that it is easy to understand the meaning at a glance, and at the same time it can increase the display distance and make the click operation more convenient. Of course, it will also occupy a certain display area. As shown below:


Display text label animation effect:


F. Zoom in icon

This is easy to understand. The icon is too small. Enlarge it as shown below:

picture


Enlarge icon animation effect:

picture



Reference address:EWSTM8 Series Tutorial 03_ Overview of the Main Window and Toolbar

Previous article:EWSTM8 Series Tutorial 02_New Basic Software Engineering
Next article:EWSTM8 Series Tutorial 04_Menu Overview (I)

Latest Microcontroller Articles
  • Download from the Internet--ARM Getting Started Notes
    A brief introduction: From today on, the ARM notebook of the rookie is open, and it can be regarded as a place to store these notes. Why publish it? Maybe you are interested in it. In fact, the reason for these notes is ...
  • Learn ARM development(22)
    Turning off and on interrupts Interrupts are an efficient dialogue mechanism, but sometimes you don't want to interrupt the program while it is running. For example, when you are printing something, the program suddenly interrupts and another ...
  • Learn ARM development(21)
    First, declare the task pointer, because it will be used later. Task pointer volatile TASK_TCB* volatile g_pCurrentTask = NULL;volatile TASK_TCB* vol ...
  • Learn ARM development(20)
    With the previous Tick interrupt, the basic task switching conditions are ready. However, this "easterly" is also difficult to understand. Only through continuous practice can we understand it. ...
  • Learn ARM development(19)
    After many days of hard work, I finally got the interrupt working. But in order to allow RTOS to use timer interrupts, what kind of interrupts can be implemented in S3C44B0? There are two methods in S3C44B0. ...
  • Learn ARM development(14)
  • Learn ARM development(15)
  • Learn ARM development(16)
  • Learn ARM development(17)
Change More Related Popular Components

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

About Us Customer Service Contact Information Datasheet Sitemap LatestNews


Room 1530, 15th Floor, Building B, No.18 Zhongguancun Street, Haidian District, Beijing, Postal Code: 100190 China Telephone: 008610 8235 0740

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京ICP证060456号 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号