You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Multiple images are loaded at runtime when using the slideshow feature
Desired Behavior
Load additional images after runtime, as needed. Perhaps implementing a --slideshow-cache argument for pre-loading a few ahead. Must bear in mind discarding used images if the cache is the same size as the entire folder.
The text was updated successfully, but these errors were encountered:
Ok, there's a solution to this, currently implemented in my PR, #235.
image_path=NULL;
update_arguments(argc, argv, longopts, optstring, true);
if (image_path!=NULL) {
if (!is_directory(image_path)) {
pthread_mutex_lock(&redraw_mutex);
img=load_image(image_path, image_raw_format);
pthread_mutex_unlock(&redraw_mutex);
}
free(image_path);
}
free(image_raw_format);
Here, when you send a --image path_to_some_image message to the API, this will load the image as it is right now. If you send it again, the image will be loaded as it is right now, not as it was before. So, replacing the current array with something like this should solve this "static" problem.
Also, doing this at short intervals is dangerous, laggy and could crash; that's why I didn't go with this idea before, but an advice should be enough.
This issue is a....
Current Behavior
Multiple images are loaded at runtime when using the slideshow feature
Desired Behavior
Load additional images after runtime, as needed. Perhaps implementing a --slideshow-cache argument for pre-loading a few ahead. Must bear in mind discarding used images if the cache is the same size as the entire folder.
The text was updated successfully, but these errors were encountered: