Traced in ComfyUI_frontend's WidgetToggleSwitch.vue: a BOOLEAN input with
on/off labels set renders as a ToggleGroup (two side-by-side buttons), not
a real switch. Without labels it renders as an actual ToggleSwitch (the
pill-shaped slider). Removing the labels so reset_bool renders as a real
switch again, matching Comfy-GGUF's keep_loaded (which never had labels).
Bump version from 1.0.12 to 1.0.13
Widget render order follows INPUT_TYPES dict order, required fields
first then optional. reset_bool sat alone in "optional", which always
trails every required field regardless of listing order - so it always
rendered last no matter what. Moved into "required" and placed first,
matching Get Image/Video File By Index's own reset_bool convention in
the sibling ComfyUI-Get-Random-File repo.
Bump version from 1.0.11 to 1.0.12
ComfyUI's node search only indexes name/display_name/search_aliases
(comfy_frontend nodeSearchService.ts) - never input/output types. None of
these nodes declared SEARCH_ALIASES, so a keyword search (e.g. "counter",
"read line") would only match if the word happened to be in the display
title verbatim.
Bump version from 1.0.10 to 1.0.11
reset_bool was typed NUMBER, which has no native widget - it rendered as
a bare (usually disconnected) socket, not something you could click.
Changed to BOOLEAN with label_on="Reset"/label_off="Off" so it renders as
an actual switch, matching ComfyUI-Get-Random-File's reset_bool convention.
Simplified the reset check from `round(reset_bool) >= 1` (needed when the
value could be an arbitrary wired number) to a plain `if reset_bool:` now
that it's a real bool, and the function default to reset_bool=False to
match. Note: any existing workflow with a NUMBER output wired into this
socket will show as disconnected on next load - this input was always
meant to be a toggle, not a numeric signal.
Bump version from 1.0.9 to 1.0.10
reset_bool set counter back to `start`, but execution fell through into
the increment/decrement branch immediately after regardless, so the
returned value on a reset call was always start + step, never start
itself - reset appeared to do nothing. Made reset an elif so it short-
circuits the step logic for that call.
Also: `elif mode == 'deccrement':` (typo, extra c) never matched the real
mode value "decrement", so decrement mode silently did nothing - fixed to
match. And number_type-vs-mode was swapped in the initial counter cast
(`int(start) if mode == 'integer' else start` - mode is never "integer",
that's number_type), so a fresh integer counter's very first value was
never actually cast to int.
Bump version from 1.0.8 to 1.0.9
This update enhances the `DirectoryFileCounter` and `TextFileLineCounter` classes by expanding environment variables in file paths using `os.path.expandvars()`. This change allows these classes to correctly handle paths that include environment variables, improving their flexibility and usability in various environments.
- **DirectoryFileCounter**: The `execute_file_counter` method now expands environment variables in the `directory_path` before performing directory operations.
- **TextFileLineCounter**: The `execute_line_counter` method now expands environment variables in the `file_path` before reading the file.
This fix ensures that paths containing variables such as `%userprofile%` are properly resolved, enabling more dynamic and environment-aware file handling.
ChrisColeTech