View Single Post
Old 01-26-2019, 07:05 PM   #19
j.p.s
Grand Sorcerer
j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.
 
Posts: 5,814
Karma: 103362673
Join Date: Apr 2011
Device: pb360
Quote:
Originally Posted by j.p.s View Post
The sqlite3 in the python package worked great.

I'll probably put together a KUAL package next weekend.
I've made a KUAL extension that works like the first post except that it sets the last access time for KUAL 999 seconds into the future, which will keep it on top for about 15 minutes.

I'll make a new thread for it and attach the extension to it tomorrow.

ETA: The extension is attached to the thread
https://www.mobileread.com/forums/sh...63#post3803463

Quote:
Originally Posted by knc1 View Post
Why not use a stored procedure to update last used time of KUAL, triggered on open, close, or 'home' button press?
I might give this a shot. My first thought was update the KUAL access time whenever the Entries database is updated, but as I type this, I guess that would cause an infinite loop of updates.

So I guess I have to learn how do detect events after all.

Last edited by j.p.s; 01-27-2019 at 12:12 PM. Reason: Add URL for the Bump KUAL thread
j.p.s is offline   Reply With Quote