digital-garbage
c338769431
Found by the adversarial pass, reproduced twice. Switching projects put the new project's numbers in the store and left the OLD ones in the controls that produce what a run actually sends. The store's own getter reported the new project correctly and the Inspector agreed, so the only place the stale value showed was the Constructor -- a window nobody has a reason to reopen after switching. Generate then ran at the size of the project you left. The attacker found it on the File-menu path. It is on three: opening from the menu, opening programmatically, and applying a pipeline change, which rebuilds every control from the PIPELINE's defaults and discards the project's. So the fix is not in the menu handler -- the store now says when a DIFFERENT project is open, which is not the same event as a field changing, and everything that follows a project is wired to that instead of to the one route in that happened to be reported. Second finding, same pass: setVideo said "nothing on screen draws from this" and did not report the change. True when written; the timeline started computing its clip widths and its ruler from that value an hour later. A comment is not a thing the next change has to keep true. Also serial-mode for the project spec: two tests making and switching projects share one real store on the dev server, and the config runs a file in parallel. A race over a JSON directory, not a bug in the app.
ComfyUI-FunPack v5 — "Cunning Cranberry"
FunPack v4.0.0 is going to be the latest release of classic FunPack. Next update is another milestone update, or shall I say, a full rework.
Maintenance of current FunPack became a mess — forgetting to add or remove buttons from/to UI, finding functions that don't do anything but still present in the code absolutely randomly, trying to keep the UI neat while it has no strict boundaries on how it should look like, and of course — making it easy for users to understand how FunPack operates and how you can operate it — this is all time, money and token-consuming.
General idea behind the FunPack v5 rework is writing it from scratch, with a new architecture where a feature can't be forgotten, where a wire can't be missed, where one failing module never stops whole process from executing. Loaders and features would tell the UI by themselves what sorts of inputs they need and where to put it — and UI will compose them according to design guidelines it would have. Samplers would become independent from features — if a feature is available and enabled, sampler would call it. If it's not — it gets skipped and doesn't even appear in the UI so it won't confuse you.
Most of this comes from a FunUI backend draft that got shelved after understanding on how much time has to be invested into polishing it. Without a community support and wide usage it would become another dead project only one person in the world needs but no one else.
Come to think of it, FunPack already became something alike, with an exception — this project is more than alive, and while I can, I will support it.
Final goal is to make FunPack an ultimate answer for a novice's question "I don't know how to generate — what do I install and how do I start?" and for a professional's question "I need a UI with all the cutting edge techniques available on day 0 — which one?"
Preparation for the v5 had started.
FunPack v5.0 "Cunning Cranberry" — coming fall 2026.
This branch is a clean start. Classic FunPack lives on main.