Hi,
The status information container is the way to go here. See
https://mail.gna.org/public/relax-devel/2010-01/msg00094.html. But
the idea is simple, one part of the code (user function) sets a
variable, and the other part (relax controller) reads it. No need to
do any text parsing of what comes out of STDOUT. The only problem
might be locking, but if this is an issue there should be something in
the threading documentation that can help. With this type of setup,
you can have the user functions place any info into the container, and
the relax controller GUI element can do with it as it pleases.
Numbers, spin name, spin index, MC sim number, etc.
Regards,
Edward
On 25 February 2010 00:26, Michael Bieri
<NO-REPLY.INVALID-ADDRESS@xxxxxxx> wrote:
Follow-up Comment #39, task #6847 (project relax):
Hi
I have something to discuss about the progress bar in the log windows.
The automatic calculation scripts are all in the auto_analysis folder and
should be used by all the interfaces. How about to add some codes for the
progress bar, so the redirect() function can read them and update, such as
it
is done with the monte carlo simulations.
I would suggest that the model-free output would give a prompt like 'Local
tm
calculation', then 'Model xx'. For the other models, it could be an output
such as 'Iteration xx'.
Similar codes could go into curve_fit and noe scripts.
What do you think about?
Cheers
_______________________________________________________
Reply to this item at:
<http://gna.org/task/?6847>
_______________________________________________
Nachricht geschickt von/durch Gna!
http://gna.org/
_______________________________________________
relax (http://nmr-relax.com)
This is the relax-devel mailing list
relax-devel@xxxxxxx
To unsubscribe from this list, get a password
reminder, or change your subscription options,
visit the list information page at
https://mail.gna.org/listinfo/relax-devel
Re: [task #6847] The Bieri graphical user interface.