Container Widget

The container widget groups other widgets together. Use it when a scene has a set of pieces that should move, layer, or score as one unit.

A container is purely structural — an invisible layout and scoring frame. While you are authoring in the studio, it shows a light dashed gray outline so you can see and grab it, but that outline is just an editing aid. In preview and for your learners, a container has no visual appearance at all — no background, border, title, or padding. If you want a visible panel behind your widgets, use a shape or image widget instead.

Why containers exist

Containers solve two common authoring problems:

• Layout grouping: A prompt, image, answer input, and hint can stay together as one visual area.
• Score aggregation: Several child answers can count as one larger task instead of several separate score items.

Without a container, each graded child widget contributes independently to scene score or lesson score. That is useful for quizzes, but less useful when several small interactions are really one combined activity.

Settings to know

A container has no appearance settings — it is invisible by design. The only controls are:

• Layout (position and size) defines the area the container occupies.
• Scoring turns the container into a single combined score item (see below).

If you want a visible frame, background, or padding around a group of widgets, add a shape or image widget behind them instead of styling the container.

Containers are not allowed inside other containers. Keep each container as a single, top-level group in the scene.

Putting widgets in a container

Placing a container over widgets doesn't put them inside it. To move a widget in, right-click it on the canvas, point at Move to Container, and choose the container by name. A widget you drag in from the Widgets tab and drop inside a container's outline joins it straight away.

To take a widget out again, right-click it and choose Remove from Container. That menu item is also a quick way to check which widgets are inside.

A container's inside is see-through in the studio too: clicking inside its outline selects whatever is underneath. To select or drag the container itself, use its name tab at the top-left corner of the outline. Its size is in the Layout section, under Show advanced layout.

How children behave

When a widget is inside a container, its position is relative to the container. The children move, appear, and layer together with their container:

• Moving or rotating the container moves or rotates the child widgets with it, and the container's opacity fades them too — the same in preview and for your learners as in the studio.
• Hiding the container hides everything inside it. That goes for the container's Visibility setting and for a behavior that runs Hide, Show, or Toggle on the container, so one action can reveal a whole group. _Example: Pop up a fact card with a Container._
• Layering: the children sit on the container's layer. Bring to front, Send to back, Bring forward, and Send backward on the container move the whole group above or below other widgets, such as a shape you placed as a background. On a widget inside the container, they reorder it among the container's other widgets.

If you delete a container (the Delete key, the toolbar, or the right-click menu) or choose Ungroup, its children are promoted back onto the scene so they do not disappear. They stay exactly where they were showing.

Scoring setup

Containers can be scored, but they score differently from normal answer widgets.

When Enable Scoring for this container is off, child widgets behave like ordinary widgets. Any scored child counts toward the scene score, the lesson score, and its grading group (if it has one) on its own.

When container scoring is on, the container owns the scores of its child widgets:

• The child widgets are still used to calculate correctness inside the container.
• A child with Scoring switched off in its own ⚙ Configure dialog is left out of the container's rule entirely. Use this for a practice item inside a graded group: answering it wrong can't fail the container, and skipping it doesn't count against the learner.
• The child widgets do not contribute separately to scene or lesson score.
• The container contributes one score item on behalf of the whole group.
• A new container is worth 0 points. Set Points when you turn its scoring on, or the group counts for nothing: its children no longer count on their own, and the container adds 0.
• The container's combined result counts toward the scene score and the lesson score, like any scored widget. Its Points setting is what it is worth, and Group adds it to a custom grading group.

This prevents double-counting. Step-by-step: Score a three-part word problem as one question. For example, three one-point questions inside a five-point container should not count as both three child points and five container points.

Aggregation modes

Aggregation mode decides when the container itself is correct.

• All children correct: Every graded child in the container must be correct. A child with Scoring off, a long answer, or a drawing (nothing grades those yet) isn't part of the rule.
• Minimum total score: The child widgets must earn at least a set number of points.
• Minimum percentage: The child widgets must earn at least a set percentage of their combined possible points.

If the aggregation condition passes, the container earns its configured point value. If it fails, the container earns zero.

Once the learner answers any graded child, a child they skip counts as wrong (zero points), both in the live score and in the final grade. The container counts as answered (for Is answered conditions and All answered checks) once every graded child in it is answered.

Useful setting combinations

• Container + scoring enabled:

The core use — one combined score for a group of related widgets, with no visible panel.

• Container + a shape or image behind it:

Add a shape or image widget to give a grouped mini-task a visible frame, since the container itself is invisible.

• Minimum percentage aggregation:

Best when a learner can miss one small part and still pass the group.

• Custom group + container scoring:

Best when a submit button should grade one grouped task without checking the rest of the scene. A group submit grades and locks only the group's widgets (and the children of a container in the group) — the other widgets on the scene stay open, and the scene itself doesn't count as submitted.

Strong use cases

• A passage with three related comprehension checks that should count as one activity.
• A matching prompt, hint, and follow-up answer grouped as one task (add a shape behind them for a visible card).
• A multi-part math problem where partial child points determine whether the full problem passes.
• A station-style scene with several independent panels, each scored as its own task.

Great pairings with other widgets

• Pair containers with text, image, and shape widgets to build clear task panels.
• Pair containers with multiple choice, text input, fill blank, or matching when several responses belong to one prompt.
• Pair containers with button when a submit action should check a custom grading group.
• Pair containers with score when you want learners to see the combined result after submission.

Related

• Score a three-part word problem as one question — step-by-step tutorial: three answers grouped and scored as one question
• Pop up a fact card with a Container — step-by-step tutorial: a card of five widgets that one button shows and another hides
• Widget State and Actions — reference for the state and actions widgets expose to conditions and behaviors
• Grading and Score