Chapter 1 Key Terms - PowerPoint PPT Presentation

1 / 36
About This Presentation
Title:

Chapter 1 Key Terms

Description:

Property. Namespace. Visual Basic uses namespaces to help the ... The Visual Basic 2003 form object has a SnapToGrid property which help in alignment. ... – PowerPoint PPT presentation

Number of Views:167
Avg rating:3.0/5.0
Slides: 37
Provided by: davidlk2
Category:
Tags: chapter | key | terms

less

Transcript and Presenter's Notes

Title: Chapter 1 Key Terms


1
Chapter 1 Key Terms
2
Assignment Statement
  • The equal sign () is the assignment operator.
  • Passes a value to a variable identified by name.
  • Causes old value to be overwritten by new value.
  • "present value is replaced by " whatever follows
    the equal sign.

3
AutoCorrect
  • Offers possible changes to misspelled words and
    common syntax errors.
  • New with Visual Studio 2005
  • Use your trial copy of Visual Studio to
    experience AutoCorrect
  • Visual Studio 2003 provides automatic assistance
    but not automatic correction

4
Camel Casing
  • Naming convention.
  • first letter of first word is lower case.
  • first letter of all other words are upper case.
  • Example

5
Class
  • Template or plan for an object.
  • Contain definitions of properties, methods, and
    events.
  • An object is an instance of a class.

6
Clean Compile
  • Upon execution, VB statements are converted to
    Microsoft Intermediate Language.
  • A "Clean Compile" is a conversion without syntax
    errors.
  • Program may still have logical errors and not
    work as planned.

7
Context Menu
  • Right click on subject of interest (like a
    control in the toolbox or a control on your
    form).
  • Note that the context menu for a control in the
    toolbox is different from the context menu for
    the same tool on your form. (different context)

8
Context Sensitive Help
  • Hit F1 and an appropriate Help window pops up if
  • pointer is on a control on the form
  • pointer is on an IDE feature
  • insertion point on a word of code.

9
Control
  • Any of the items in the Windows Forms tool box.
  • They are classes of objects that help a user
    interact with the application.
  • (the user is the person who will use the
    application that you create)

10
Debug Time
  • The mode assumed when debugging is paused.
  • Errors
  • Breakpoints

11
Declaration Section
  • The place in code where variables are declared.
    (Dim)
  • Declarations may be found throughout the code but
    often found at the top of the page.
  • Variable scope is related to declarations.
  • Remarks are appropriately made above the
    declarations but may be placed anywhere in the
    code.

12
Scope
  • Where everybody knows your name.
  • Where in the code particular identifiers are
    recognized and have value.
  • More later.

13
Design Time
  • The mode of Visual Basic when you are designing
    the form or writing code.

14
Document Window
  • This is where you will design forms and write
    code.
  • Notice that it is tabbed so you can easily switch
    between form design and code presentations.
  • You can even bring up other files into the
    document window for reference.

15
Express Edition
  • Bill Gates accommodates several market targets
    with "custom" versions of Visual Basic.
  • The matrix of features in found in Help Contents
    gt Introducing Visual Studio.NET gtVisual Studio
    .Net Editions.

16
Event
  • Action on the system taken by the user.
  • Clicking on a mousekey.
  • Pressing a key on the keyboard
  • Loading a form
  • Closing a form
  • Causes an event procedure (subroutine) to run.
  • Event procedures can be triggered by other
    objects in the program.

17
Event Procedure
  • Basically a block of Visual Basic code that runs
    when triggered by a system event.
  • Must start with Private Sub and must end with End
    Sub.

Private Sub nextButton_Click(ByVal sender As
System.Object, ByVal e As _ System.EventArgs)
Handles nextButton.Click If
ItemNumber lt LastItemsAdded Then
ItemNumber ItemNumber 1
ClearRadioButtons()
ShowItem(ItemNumber) End If End Sub
18
Form
  • A Windows graphical user interface (GUI) object
  • WSIWYG

19
Form Designer
  • Part of the Integrated Design Environment that
    allows you to design a Windows form.
  • Allows you to place and resize visual objects on
    the form.
  • Allows you to set the properties of objects on
    the form at design-time although properties may
    be changed at run-time.

20
Graphical User Interface.
  • A window containing controls that can be
    activated by the user.
  • Also may provide a facility for obtaining user
    input data and providing output data.

21
Handle
  • (Has multiple meanings in VB)
  • The markers for relocating or resizing objects

Selection Boarder
22
Label
  • A "control" object for displaying information.
  • Not appropriate for input.(use TextBox instead.

23
Logic Error
  • When compilation is clean but the resulting
    application does not work as planned.
  • For instance, your arithmetic may be flawed.

24
Me
  • The collection of the objects.
  • It may refer to the form.
  • Usually not required.

25
Method
  • An active capability of an object.
  • For properties we think adjectives but for
    methods we think verbs.

dot
Property
Method
26
Namespace
  • Visual Basic uses namespaces to help the
    programmer find a particular object.
  • More Later.

27
Object Oriented Programming
  • Basically, the user controls the flow of the
    program.

28
Object
  • Components of Visual Basic programs.
  • An object is created from a class.
  • Objects have specific events, properties, and
    methods defined by the class.

29
Project File
  • A text file, you can read it with Notepad
    Describes the project.
  • Lists all of the files included in the project.

30
Properties Window
Control
the properties
explanation
31
Pseudocode
  • English words that describe the action you want
    the application to take.
  • It is not formalized, you make it up as you go
    along.
  • It is used in the planning stages of the
    application design.

32
Remarks
  • Comments embedded in the code for explanation and
    clarification of the code.
  • Helpful for later modification of the code.
  • Header comments may contain
  • The purpose of the program
  • Name of programmer or team
  • Date written or modified
  • Begin each remark line with apostrophe.

33
Run-time error (exception)
  • Halts execution of the program.
  • Impossible arithmetic
  • Missing files
  • Run can sometimes be rescued by code that
    responds to the condition.

34
Snap Lines
  • The Visual Basic 2003 form object has a
    SnapToGrid property which help in alignment.
  • Snap lines do not exist in this version.

35
Solution
  • A Visual Basic application
  • May contain one or more forms.

36
Solution Explorer Window
Files in the project.
Write a Comment
User Comments (0)
About PowerShow.com