> Hi,
> I wrote a week or so ago about detecting updates.
> You mentioned that the best way is to make a new 
> callback and said you'd put it on your todo list.
> I'm sure this todo list of yours is getting REALLY 
> long, so I tried to find where I could put such a 
call 
> back inside htsback.c and/or htscore.c. There are 

Humm, a log callback might be interesting - anyway, 
the 'updated' callback will be included for the next 
release - and besides parsing log strings might be 
tough, too :)