Graphical User Interface Programming practice questions

root.close()

Why it fails: close() is not a method of the Tk object.

root.exit()

Why it fails: exit() is not part of the Tkinter namespace.

root.quit()

Why it fails: quit() stops the mainloop but may not fully destroy the window instance immediately.

fill='all'

Why it fails: The 'all' string is not a valid parameter for fill.

fill='both'

Why it fails: Tkinter expects the constant tk.BOTH, not a lowercased string.

fill=tk.EXPAND

Why it fails: tk.EXPAND is used for the expand parameter, not fill.

editable=False

Why it fails: editable is not a standard Tkinter option.

enabled=False

Why it fails: enabled is not a valid option.

readonly=True

Why it fails: readonly is not a valid configuration option for most widgets.

widget.hide()

Why it fails: There is no hide() method.

widget.remove()

Why it fails: There is no remove() method.

widget.delete()

Why it fails: delete() is for clearing widget content, not for hiding it.

<Key-Up>

Why it fails: Tkinter event strings are case-sensitive and lowercase, so the release event is <KeyRelease>; <Key-Up> matches no binding. It tempts because hyphenated modifier syntax like <Control-Key-a> exists, suggesting a Key-Up pattern, but no such event name is registered, so bind() silently accepts a sequence that never fires.

<ReleaseKey>

Why it fails: Tkinter names the key-release event <KeyRelease>; <ReleaseKey> is not a recognised event string, so bind() registers a sequence that never triggers. It tempts because the wording mirrors the requirement directly, and descriptive names feel natural, but Tk event names are fixed identifiers, not free-form descriptions of the action.

<KeyUp>

Why it fails: Tkinter event names are lowercase and case-sensitive; the correct string is <KeyRelease>, so <KeyUp> matches nothing and the callback never fires. It tempts because KeyUp is the standard name in JavaScript and other GUI toolkits, making it feel familiar, but Tkinter uses KeyRelease rather than KeyUp.

FloatVar

Why it fails: This class does not exist; DoubleVar is used for floats.

CharVar

Why it fails: This class does not exist.

It requires absolute pixel positioning.

Why it fails: That describes the place() manager.

It only supports a single column layout.

Why it fails: It supports arbitrary rows and columns.

It cannot be mixed with the pack manager in the same parent.

Why it fails: You can use both, but not on the same widget instance.

readonly

Why it fails: Readonly is a state for specific widgets, not a general widget state property.

hidden

Why it fails: Hidden is not a standard state value.

widget.pack(fill='x', expand=True)

Why it fails: The question specifies grid(), but pack() is a different geometry manager; mixing them in one container raises a TclError, and pack() cannot satisfy a grid() requirement. It tempts because fill='x' with expand=True genuinely stretches a widget horizontally, which is the correct pack() idiom for this effect.

widget.grid(sticky='nsew')

Why it fails: Sticky='nsew' anchors the widget to all four cell edges, but without columnconfigure(weight=1) on the parent column, the cell itself never grows, so no extra horizontal space reaches the widget. It is tempting because sticky is the standard way to make a widget fill its grid cell, and it would work once the column is given non-zero weight.

widget.grid(padx=10, pady=10)

Why it fails: Padding adds space but does not handle expansion behavior.

Call root.update() inside the calculation loop.

Why it fails: This is inefficient and often leads to unstable GUI behavior.

Increase the root.after() delay time.

Why it fails: This just delays the execution and does not prevent freezing during the calculation.

Wrap the calculation in a try-except block within the button command.

Why it fails: Error handling does not address the blocking nature of the main thread.

difficulty

Why it fails: Not applicable.

handler(event.keysym)

Why it fails: The 'keysym' attribute gives the name of the key (e.g., 'Return'), not the character itself.

handler(event.get_char())

Why it fails: There is no 'get_char' method on the event object.

handler(event.key)

Why it fails: The event object does not have a 'key' attribute.

difficulty

Why it fails: Not applicable.

frame.pack(anchor='s', expand=True)

Why it fails: Anchor is used for positioning within allocated space, not for docking sides.

frame.pack(side='bottom', expand=False)

Why it fails: While it docks to the bottom, without fill, it won't occupy the full width.

difficulty

Why it fails: Not applicable.

frame.grid(row=99, column=0)

Why it fails: Grid is not pack; this relies on row indexing which is less robust for docking.

difficulty

Why it fails: Not applicable.

Message

Why it fails: Message is an older, less flexible widget for text display.

Entry

Why it fails: Entry is for single-line input only.

Label

Why it fails: Label is for short text and does not support easy multi-line formatting or selection.

difficulty

Why it fails: Not applicable.

menu.add_menu()

Why it fails: There is no add_menu method.

menu.add_command()

Why it fails: This adds a clickable menu item, not a sub-menu.

menu.add_submenu()

Why it fails: There is no add_submenu method.

widget.rebind()

Why it fails: There is no rebind() method; you simply call bind() again to override.

widget.reload()

Why it fails: There is no reload() method in Tkinter widgets.

widget.refresh()

Why it fails: There is no refresh() method in Tkinter widgets.

treeview.see(item)

Why it fails: The see() method ensures that the specified item is visible by scrolling the treeview if necessary. It does not change the expansion state of any item. It is used to bring an item into view, not to expand its descendants. Therefore, it is not the correct method for expanding nodes.

treeview.expand(item)

Why it fails: The expand() method expands only the specified item, not its descendants. To expand all children, you would need to call expand() recursively on each child. While it is part of the solution, it does not by itself expand all nodes under the selected item. The question asks for a method that expands the item and all its descendants, which expand() does not do automatically.

treeview.item(item, open=True)

Why it fails: The item() method with open=True expands or collapses a single item, but it does not recursively affect its children. To expand all descendants, you would need to iterate over each child and call item() individually, which is inefficient and requires manual traversal. This method alone does not fulfill the requirement of expanding all nodes under a selected item.

text.grid(sticky='nsew', padx=10, pady=10) with root.rowconfigure(0, weight=1) and root.columnconfigure(0, weight=1)

Why it fails: grid with sticky='nsew' and weighted row/column does stretch the widget, but this option omits the calls to configure the row and column weights shown in the option text itself; without them grid will not distribute extra space, so the Text widget stays at its requested size and the margins alone do not produce the required behaviour.

text.place(relx=0.5, rely=0.5, relwidth=1.0, relheight=1.0)

Why it fails: place with relative width and height of 1.0 makes the widget cover the entire parent, so no 10-pixel margin is preserved. The padx and pady options are ignored by place, which means the widget will touch or exceed the window edges, violating the requirement of a constant margin on every side.

text.pack(side=tk.LEFT, fill=tk.X, expand=True) and text.config(width=80, height=24)

Why it fails: fill=tk.X stretches only horizontally, so vertical resizing is not handled, and the fixed width and height in characters conflict with dynamic resizing. Also, side=tk.LEFT places the widget against the left edge without reserving equal margins on all sides, so the 10-pixel border requirement is not met.

Use the command parameter of add_command to specify the function to call when the menu item is selected.

Why it fails: The command parameter is used to specify the function that runs when the menu item is clicked. While this is necessary for the menu item to perform the Quit action when clicked, it does not relate to the keyboard shortcut. The question asks for steps to implement the accelerator, so this is not one of them.

Create a Menu widget and add it to the root window using root.config(menu=menubar).

Why it fails: Creating a Menu widget and configuring it as the root's menu is necessary to display the menu bar, but it is not specific to adding a keyboard shortcut for the Quit command. This step is part of general menu setup. While required for the menu to appear, it does not by itself implement the accelerator functionality.

Set the tearoff parameter to 0 when creating the File menu.

Why it fails: The tearoff parameter controls whether the menu can be detached from the main window. Setting it to 0 prevents tearing off, which is a cosmetic preference. It has no effect on keyboard shortcuts or the Quit command's functionality. Therefore, it is not necessary for implementing the accelerator.

The Checkbutton must be packed or gridded before the variable is created, otherwise the `variable` link is never established.

Why it fails: Geometry management has no effect on variable binding. The `variable` option is processed when the widget is constructed, not when it is placed. Creating the variable before the widget is the correct order, and the placement method is irrelevant. This distractor confuses layout with data binding, which are independent concerns in Tkinter.

The `variable` option is ignored for Checkbuttons unless the widget is also given a `command` callback that manually calls `set()`.

Why it fails: The `variable` option is fully honored by Checkbutton without any callback. The widget updates the linked Tkinter variable on every toggle. A `command` callback is only for running application logic when the state changes; it is not needed for synchronization and does not repair a variable-type mismatch. Adding one here would only hide the real issue.

The Checkbutton's `onvalue` and `offvalue` options must be set to the strings 'True' and 'False' for the state to be reflected in the variable.

Why it fails: Setting `onvalue` and `offvalue` to string literals would still store those strings in the variable and would work, but it is not required. By default the Checkbutton stores 1 and 0, and a StringVar converts those to '1' and '0', which do change. The real problem is that the variable type does not match the default integer values the Checkbutton writes, so the state is written but not in a form the developer expects.

The `filetypes` list should be passed as a tuple of tuples with the pattern first and description second, e.g. `(('*.png', 'PNG'),)`, to activate hard filtering.

Why it fails: The order of pattern and description does not change filtering behavior; both orders are accepted by Tk. Reversing them will not prevent a user from typing a different filename. The real limitation is that native dialogs treat `filetypes` as a convenience filter, not a security boundary, so this change does not solve the problem.

The `filetypes` option is only a display filter; you must validate the returned extension in code or use `askopenfilename` with a custom `validatecommand` to enforce the restriction.

Why it fails: Native file dialogs do not support a `validatecommand` option; that belongs to Entry widgets. The first part of the statement is true, but the suggested fix is invalid for `askopenfilename`. The realistic enforcement is post-selection validation in Python, not a dialog-level validator, making this option misleading despite containing a kernel of truth.

The dialog must be created with `FileDialog` directly and `mode='r'` set, because `askopenfilename` bypasses extension filtering entirely.

Why it fails: `askopenfilename` is a convenience wrapper that does apply the `filetypes` filter for display; it does not bypass filtering. Using the `FileDialog` class directly gives more control but does not add hard extension enforcement either. This distractor invents a behavioral difference that does not exist and would not fix the reported issue.