Before we had a compile flag that enabled compiling against gdk instead of imlib. As a side effect the caching "problem" was not there and it provided an option to compile awesome with less dependencies (since I think its fair to say that gdk is more widespread than imlib since anything from gimp, going through firefox, pidgin, gdm and all of gnome depends on it). And we could load some nice formats like svg (which imlib does not handle) and allow graceful rescaling.
Perhaps we should renable this option? I don't remember why it was removed. Cheers, Alex On Tue, Mar 24, 2009 at 3:53 PM, awesome <[email protected]> wrote: > THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. > > A new Flyspray task has been opened. Details are below. > User who did this - Alex Rez (realx) > Attached to Project - awesome > Summary - dynamic image in imagebox > Task Type - Feature Request > Category - Wibox > Status - Unconfirmed > Assigned To - Operating System - All > Severity - Medium > Priority - Normal > Reported Version - 3.2 > Due in Version - Undecided > Due Date - Undecided > Details - I try to load some dynamic image in imagebox (see picture - > http://sochi.biz/rrd/), > but as far as I know, the library imlib2 caches by default the image by > the file name and, after the image has been loaded, the second request > takes the information from the cache in spite of the changed time stamp. > Is there a possibility to avoid caching not using > imlib_image_set_changes_on_disk or imlib_load_image_without_cache? > > More information can be found at the following URL: > http://awesome.naquadah.org/bugs/index.php?do=details&task_id=481 > > You are receiving this message because you have requested it from the > Flyspray bugtracking system. If you did not expect this message or don't > want to receive mails in future, you can change your notification settings > at the URL shown above. > > -- > To unsubscribe, send mail to [email protected]. > -- To unsubscribe, send mail to [email protected].
