On Thursday, July 14, 2011 15:37:58 Jonathan Stroud wrote:
> On Jul 14, 2011, at 1:45 PM, Mike Frysinger wrote:
> > On Thursday, July 14, 2011 14:35:08 Jonathan Stroud wrote:
> >> Here is a crude patch for the callback.
> > 
> > this should be unnecessary with the patch i posted.  you can already
> > override the urj_log_state.progress func and that gets called at all the
> > progress points ...
> > 
> > also, please dont top post in your replies.
> 
> Perhaps I am misunderstanding.  It looked to me like your code just prints
> a progress bar to stdout using the existing log functions.
> 
> I was adding an optional method to add a callback so, say, a python script
> could set a callback and handle showing the progress anyway it liked,
> perhaps with a gui or piping out to zenity.

take a look at urj_log_state_t.  all logging goes through this structure of 
function pointers.  its designed for apps to arbitrarily set these to their 
own entry points so they can capture all logging output.

the progress patch does the same thing.  so your python code could set this 
pointer, and then you'd see all the progress points: start, update, update, 
update, finish.  no need to modify the urjtag code at all.
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.

------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
UrJTAG-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/urjtag-development

Reply via email to