参数控制面板 (Parameter Control Panel)

This is the node three others in this pack are built to consume. On its own it's almost embarrassingly simple - no required inputs, no optional inputs, one output - but its whole point is what happens downstream of it.

What it does

Parameter Control Panel is a pure UI node: it exists to hold a set of controls you define through its own front-end panel (the pack's README describes several nodes shipping their own settings dialogs and panels as JS frontend extensions, and this is the flagship example of that pattern). Whatever values you set on that panel get packed into a single output, parameters, typed as a DICT. That's the entire declared schema - zero required fields, zero optional fields, one output.

The reason that's useful rather than useless is what this pack gives you to unpack it with. Wire parameters into Parameter Break to explode the whole bundle back into up to 32 individually-typed wires, one per control. Or, if a single control on your panel is a dropdown-style choice, its currently-selected value is the kind of thing Enum Switch expects for its enum_value field, letting a dropdown you built here drive actual branching logic elsewhere in the graph.

Why bother with this instead of loose Primitive nodes

The practical case for this pattern is the same reason it exists in other node ecosystems too: once a workflow has more than a handful of user-facing controls, scattering them as individual Primitive nodes across the canvas makes the graph hard to read and easy to break when you rewire something. Consolidating them into one panel, routed as a single wire until you actually need an individual value, keeps the controls in one place and the wiring simple. It's also the shape you want if you're planning to expose a workflow's "settings" to someone else running it - one panel to fill in, rather than a dozen loose nodes to hunt down.

The inputs and outputs that matter

• No required or optional graph inputs - everything is configured through the node's own on-canvas panel.
• parameters (output, DICT) - the packed bundle of whatever you set on the panel. Feed it to Parameter Break to unpack, or read individual values off it wherever a dict input is expected.

How to install it

ComfyUI Manager: search "ComfyUI-Danbooru-Gallery", install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/Aaalice233/ComfyUI-Danbooru-Gallery.git
cd ComfyUI-Danbooru-Gallery
pip install -r requirements.txt

Restart ComfyUI.

Common issues & troubleshooting

Panel doesn't load, or the node appears with no controls. This pack's UI panels register as a separate JS frontend extension (WEB_DIRECTORY) alongside the Python node code, and the two can fail independently - check the ComfyUI startup log to confirm the web directory registered successfully, then try a hard browser cache clear and refresh, which is the same fix the pack's own FAQ suggests for its other panel-driven nodes.

Downstream Parameter Break outputs look shifted or wrong. The order of values inside parameters follows however you built the panel - add, remove, or reorder a control here and the corresponding output_N slots on Parameter Break shift to match. If something downstream looks off after editing the panel, that's the likely cause.

Node doesn't show up in the add-node menu at all. Standard pack-load check: confirm the repo path is ComfyUI/custom_nodes/ComfyUI-Danbooru-Gallery, confirm dependencies installed cleanly, and check the console for an import error on restart.