If the face just deleted (or rejected) was the final face associated with a tag, then the Tag Icon associated should be removed. Hence it’s important to enable Automatic Removal of Tag Icons, as it would allow re-Assignment of a different face to the Tag. In case the User accidentally confirms a Face, this would lead to automatic assignment of the wrong face to a tag. Initial implementation for Auto Icon Assignment.To get around this problem, I included Automatic Icon Assignment in higher-level classes (such as FaceUtils), and made use of QTimers to ensure that the lower level Database functions (sometimes in different threads), were completed before trying to assign a tag. Functions of AlbumManager can only be used in files that are compiled with AlbumManager ( gui_digikam_obj), and since Database functions are pretty low level, they aren’t compiled with AlbumManager.
People Tags are defined as Tag Albums ( TAlbums) in the DigiKam database, as such there already exist methods for assignment of Album Icons ( updateTAlbumIcon) provided by the AlbumManager class.Ĭonfirming and Rejecting faces ultimately happens at the Database level, which led to a problem. A similar process can be implemented in the reverse process, that is if the User deletes the last Face associated with the Tag, then the Tag Icon should be deleted. Generating aspect ratio crops in digiKam for use with particular monitor size or shape. Adding Textures To Your Images Using digiKam Some images look a little flat and benefit from the addition of a texture. Add a dramatic effect by a simple toning technique. The new Geolocation interface (Image -> Geo-location) aggregates all geotagging tools in one place. Convert Photos to Black and White with digiKam shows you the tools for quick results. These two processes can be easily automated, so that whenever a new Tag is created (as a consequence of Face Confirmation), then the Face is automatically assigned as the Tag Icon. Transcribed from Dmitri Popovs blog, 24 March 2011 Geolocation is not a new feature, but in digiKam 2.0 it has been thoroughly reworked to streamline the process of geotagging photos. If neither of these work, then I don't know what that program did to make it's libraries load first and you'll have to wait for someone more knowledgeable to take an interest in this problem.This can be annoying for the User if there are a large number of Tags. Regenerate the library loader cache with 'sudo ldconfig'. If there's a line giving that directory as a source for libraries, use an editor and put a '#' at the beginning of that line. If there's no LD_LIBRARY_PATH (or unsetting it didn't help), check '/etc/ld.so.conf' and the files in '/etc/ld.so.conf.d'. If that works, check the startup files of the shell for a line defining the variable and delete it or comment it out.
If it's in there, try unsetting that variable ('unset LD_LIBRARY_PATH') and starting digikam from the shell. The libs in that directory are different versions from the ones in the repositories and a program expecting the standard versions of the libraries will find them unusable and abort.Ĭheck whether the environment contains a variable 'LD_LIBRARY_PATH' ('echo $LD_LIBRARY_PATH') with a value containing that directory. The symptoms may show with digikam, but the problem is with whatever program put a couple of libraries in '~/anaconda3/lib/' and configured the system to look there first when searching for libraries.
0 kommentar(er)
