ComfyUI Node: Preview History (Raffle)

Preview History (Raffle):

The PreviewHistory node is designed to manage and generate previews of image files within a specified directory, primarily focusing on .png files. Its main purpose is to facilitate the organization and display of image previews in a user interface, making it easier for you to browse through your image history. By sorting images based on their modification times, it ensures that the most recent images are prioritized for preview. This node also handles the cleanup of older files, maintaining a manageable history size by removing excess files. This functionality is particularly beneficial for AI artists who need to keep track of their generated images over time, providing a streamlined way to view and manage their creative outputs.

Preview History (Raffle) Input Parameters:

history_folder

The history_folder parameter specifies the directory path where the image history is stored. It is crucial for the node's operation as it determines the location from which images are retrieved and managed. The node scans this folder for .png files, sorts them by modification time, and generates previews accordingly. There are no specific minimum or maximum values for this parameter, but it should be a valid directory path accessible by the system.

history_size

The history_size parameter defines the maximum number of image files to retain in the history. It directly impacts the node's execution by determining how many of the most recent images are kept for preview purposes. Files exceeding this number are removed to maintain the specified history size. The minimum value is 1, and there is no explicit maximum, but it should be set according to your storage capacity and needs.

Preview History (Raffle) Output Parameters:

ui

The ui output parameter is a dictionary containing a list of image previews. This output is crucial as it provides the data necessary for displaying image previews in the user interface. Each entry in the list represents a preview of an image file, allowing you to visually browse through your image history. This output helps in quickly identifying and selecting images for further use or analysis.

Preview History (Raffle) Usage Tips:

• Ensure that the history_folder is correctly set to the directory where your images are stored to avoid any issues with file access.
• Adjust the history_size parameter based on your needs and available storage to efficiently manage the number of images retained for preview.

Preview History (Raffle) Common Errors and Solutions:

[ Preview History (Raffle)] Warning: Could not access file <full_path> during scan.

• Explanation: This error occurs when the node is unable to access a file in the specified directory, possibly due to permission issues or the file being in use by another process.
• Solution: Check the file permissions and ensure that no other applications are using the file. Verify that the directory path is correct and accessible.

[ Preview History (Raffle)] Warning: File <history_file_path> not found during preview generation (maybe removed?). Skipping.

• Explanation: This warning indicates that a file expected to be in the history folder is missing, possibly due to manual deletion or a misconfigured path.
• Solution: Verify that the file path is correct and that the file exists in the specified directory. If files are being deleted manually, ensure that this is done with consideration of the node's operation.

[ Preview History (Raffle)] Error processing history image '<history_file_path>' for preview: <error_message>. Skipping this image.

• Explanation: This error suggests that there was an issue processing a specific image file, which could be due to file corruption or unsupported file format.
• Solution: Check the integrity of the image file and ensure it is a valid .png file. If the file is corrupted, consider replacing it with a valid version.

[ Preview History (Raffle)] Error saving new image to '<history_folder>': <error_message>``

• Explanation: This error occurs when the node fails to save a new image to the specified directory, possibly due to insufficient permissions or disk space.
• Solution: Ensure that the directory has write permissions and that there is enough disk space available. Check for any restrictions that might prevent file writing.