winforms Flashcards

1
Q

you can create radio button menu items within a group. When one radio button item is
checked, the others in the same group are automatically unchecked.

A

Radio Button Items

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

are commonly used to allow users to input and edit text.

A

TextBoxes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

You might want to perform certain actions the user interacts with the TextBox. Common events include
TextChanged or KeyPress.

A

Event Handling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Represents the name of the control, which can be used to reference it in code.

A

NAME

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

gets or sets the current text in the TextBox.

A

TEXT

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Determines whether the TextBox can display more than one line of text. If set to true, the TextBox
can have multiple lines.

A

Multiline

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Specifies the character to be displayed in password input.

A

PasswordChar

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Specifies whether the TextBox should display scrollbars. Options include None, Horizontal,
Vertical, and Both.

A

ScrollBar

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Gets or sets a value indicating whether pressing the Enter key in a multiline TextBox control
creates a new line of text.

A

AcceptsReturn

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Gets or sets a value indicating whether pressing the Tab key in a multiline TextBox control types
a tab character in the control instead of moving the focus to the next control in the tab order.

A

AcceptsTab

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Gets or sets the border style of the TextBox. Options include None, FixedSingle, and Fixed3D.

A

BorderStyle

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Gets or sets whether the TextBox control automatically converts characters to uppercase,
lowercase, or leaves them unchanged.

A

CharacterCasing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Gets or sets whether to use the system password character for password input.

A

UseSystemPasswordChar

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

gets or sets whether the TextBox control automatically wraps words to the beginning of the
next line when necessary.

A

WORDWRAP

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

gets or sets a value indicating whether the control is visible.

A

VISIBLE

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

gets or sets the tab order of the control.

A

TABINDEX

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Occurs when the mouse pointer enters or leaves the control.

A

MouseEnter, MouseLeave

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Occurs when the control receives or loses focus.

A

GotFocus, LostFocus

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Occurs before and after the control validates its data.

A

Validating, Validated

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Events associated with the form’s lifecycle.

A

FormLoad, FormClosing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Occurs when the control is clicked.

A

Click

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Occurs when the control is double-clicked.

A

DoubleClick

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Occurs when the Text Property of the control changes.

A

TextChanged

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Handle Keyboard input events.

A

Keypress, KeyDown, KeyUp

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Design a foolproof and user-friendly interface. Place each control logically, use consistent naming conventions and provide clear labels.
UI Design
26
Implement proper validation for user inputs. Validate data on both the client and server sides to ensure data integrity.
Data Validation
27
Handle errors gracefully. Display informative error messages to users and log detailed errors for developers.
ERROR HANDLING
28
Uses data binding to connect controls to the data source. This simplifies the process of displaying and updating data.
Data Binding
29
Handle user interface events effectively. Implement event handlers to respond to user actions like button clicks and text changes.
Event Handling
30
Maximize other form controls such as containers, panels, and group boxes to related controls.
Form Layout
31
Design an efficient navigation flow between forms. Use menus, toolbars, and buttons for navigation.
Navigation
32
Ensure that your application is responsive and performs well. Consider multithreading for time-consuming tasks to prevent UI freezes.
Responsive Design
33
Implement security measures to protect sensitive data. Avoid SQL injection, se parameterized queries, and encrypt sensitive information.
Security
34
Organize your code into logical classes and methods. Follow best practices for code readability and maintainability.
Code Organization
35
Document your code and provide inline comments. This helps other developers understand your code and makes maintenance easier.
Documentation
36
Perform thorough testing, including unit testing and user acceptance testing. Identify and fix bugs before releasing the application.
Testing
37
Design your application to be accessible to users with disabilities. Ensure that controls are keyboard accessible and provide alternative text for images.
Accessibility
38
Design your application to handle growth. Consider scalability in terms of data volume, user load, and future feature additions.
Scalability
39
Plan for localization from the beginning. Separate user interface strings from code to make it easier to translate your application into different languages.
Localization
40
Use version control systems. (e.g., Git) to track changes in your codebase. This helps in collaboration and version management.
Version Control
41
button controls are primarily used for user interaction. Users click a button to perform actions, such as submitting a form, saving data, or triggering a specific event in the application.
USER INTERACTION
42
Buttons are equipped with event handlers, such as the Click event, which allows you to specify what should happen when the button is clicked. You can write code to respond to button clicks, making them highly customizable.
EVENT HANDLING
43
Button controls should be designed with accessibility in mind. This includes providing a keyboard shortcuts.
ACCESSIBILITY
44
Buttons are commonly used for dialog boxes and forms to close or confirm actions, such as OK, Cancel, Yes, No, and Apply buttons. They play a crucial role in user-friendly interface design.
DIALOG BUTTONS
45
Buttons typically display text, but they can also display images or a combination of both. You can customize the button’s text, font, color, and appearance to match the application’s design.
TEXT & APPEARANCE
46
In radio button groups, users can select one option from a set of mutually exclusive options. Clicking a radio button deselects the others in the same group.
RADIO BUTTON
47
A typical button is used to perform actions in the application. It’s often labeled with descriptive text like “Submit”, “Save”, or “OK”.
STANDARD BUTTON
48
checkboxes allow users to select multiple options from a set of choices. Each click toggles the checkbox’s state (checked or unchecked).
CHECKBOXES
49
they have two states, such as “On” and “Off”, and they are used to switch between two options or modes.
TOGGLE BUTTON
50
maintain consistency in button design, such as using a uniform style, size, and alignment throughout the application.
CONSISTENCY
51
position buttons logically in forms and dialogs. The primary action button, such as “OK” or “Submit”, should typically be the default button that activates when the user presses Enter.
BUTTON PLACEMENT
52
Use clear and descriptive labels on buttons to help users understand the action that will be performed when they click.
DESCRIPTIVE LABELS
53
Ensure that keyboard users can interact with buttons by providing keyboard shortcuts and appropriate focus behavior.
KEYBOARD ACCESSIBILITY
54
use buttons for actions like “cancel” or “Close” to allow users to exit dialogs or cancel operations without data loss.
ERROR HANDLING
55
Test Button functionality thoroughly to ensure that they behave as expected and don’t produce unexpected side effects.
TESTING
56
Consider localization and ensure that button labels are translated for international users.
LOCALIZATION
57
In Windows Forms (WinForms) applications, you can create a menu list using MenuStrip. MenuStip control provides a convenient way to create menus and submenus in your application’s user interface.
MenuStrip
58
is a class in Windows Forms that represents a menu item within a MenuStrip or a context menu(created with ContextMenuStrip).
ToolstripMenuItem
59
allows you to define keyboard shortcuts for menu items, which are activated when the user presses the specified key combination.
ShortcutKeys
60
you can enable or disable menu items using the Enabled property. Disabled menu items are displayed grayed out and cannot be interacted with.
Enabled and Disable Items –
61
You can create separator lines between menu items to visually group them or separate them. This is done by adding ToolStripSeparator controls to the DropDownItems collection.
Separator Lines
62
you can create radio button menu items within a group. When one radio button item is checked, the others in the same group are automatically unchecked.
Radio Button Items