[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-patch-tracker] [patch #8016] Prototype octave_value_list transfe
From: |
Dan Sebald |
Subject: |
[Octave-patch-tracker] [patch #8016] Prototype octave_value_list transfer |
Date: |
Mon, 15 Apr 2013 03:13:02 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 |
Follow-up Comment #1, patch #8016 (project octave):
Will try something like this at a later time:
octave_value_list result = eval_string(...,nout)
if (OK)
for i=0; i< nout; i++
{
copy_count(i) = result(i).rep.count;
result(i).rep.count = -1;
}
emit command_result (result)
put_thread_to_sleep()
//Restore the count
for i=0; i< nout; i++
{
result(i).rep.count = copy_count(i);
}
None of the copy/deletes going on in the signal/slot mechanism will have any
effect on the rep-count. In the GUI thread would be:
octave-link::handle_command_result (QObject *ID, octave_value_list& result)
{
// Transmit result to other objects in GUI.
emit have_command_result (ID, result);
// No longer need this data
wake_up_the_worker_thread()
}
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/patch/?8016>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/