-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update imageFeed.js #224
Update imageFeed.js #224
Conversation
This is a aewrite of the Image Feed system based on my previous abandoned pull request. The feed: - lets the user filter images based on source node. - groups images from the same run into batches with a visible marker. Additionally, the slider for height as well as two new controls have been moved to the ComfyUI menu. Locking the feed to the left or right has not yet been implemented. Known 'image nodes' are defined in an array, with unrecognised nodes caught via a catch fall filter setting.
The big weakness of this implementation is that I haven't found a way to dynamically identify 'image' nodes. There's a 'custom node' fallback, but this is deeply unsatisfying. All feedback is welcome, but feedback on that issue specifically is extra welcome. |
Fixed minor logic bug in execution_start.
Fix divider bar CSS.
Fixed bug I created in legacy getVal's
Fixed custom node button interactions with filter.
Updated getVal so it actually works the way I thought it did.
More bug squashing.
Dealing with other peoples problems.
Hey, thanks, would you please be able to split the different parts into their own PRs (probably: batch markers, filtering nodes, ui refactor changes), as its difficult to review with everything all in one. For some early feedback:
|
This is a (somewhat over the top) rewrite of the Image Feed system based on my previous abandoned pull request.
The feed:
Additionally, the slider for height as well as two new controls have been moved to the ComfyUI menu.
Locking the feed to the left or right has not yet been implemented but I can readd it if its a 'must go' feature.
Known 'image nodes' are defined in an array, with unrecognised nodes caught via a catch fall filter setting. I'm currently looking for a better way to identify 'image' nodes for inclusion in the filter.
Tested on Firefox and Chromium.