View Single Post
Old 03-21-2011, 06:01 AM   #117
Iņigo
Guru
Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.
 
Posts: 730
Karma: 72743
Join Date: Feb 2008
Location: Here or there
Device: iRex iLiad, iRex DR800S. K4NT. Kobo Aura, Aura One, Libra 2.
Quote:
Originally Posted by Mackx View Post
The 'zoom-data' is stored in the local databases that are in each folder. They are called metadata.db. See the 'application_data' table, which contains a list of file_id/key/value entries. The 'file_metadata'-table can be used to link the file_id to a filename.
The zooming factor is stored in keys named: 'uds_zoom_factor'.

When 'Indexing files' is shown on the display, a program called mdbindex is executed. The sources are in iRex\Sources\4.0\iRex\ctb\src together with the source code of ctb. See the makefile to see which files are used.
The main functionality is in a function called index_full() in the file index.c. Which first reads all data from global.db, then all data form the SD-card and then updates global.db with all changes (added files/removed files). It does not touch the local metadata.db files, so zooming factors are not modified.

I hope this information is usefull.

So next steps is to try to figure out how the uds_zoom_factor is used by UDS.
Take a look at this thread: https://www.mobileread.com/forums/showthread.php?t=93466
Specially post #4: run "dbus-monitor" on the emulator shell, zoom on the emulator screen and see if the zoom factor is passed.

Hope it helps,
Iņigo
Iņigo is offline   Reply With Quote