Achilleas,
you can put feature requests on our issue tracker, where they are less
likely to get lost than in our list archives. There's also the roadmap:
http://gnuradio.org/redmine/projects/gnuradio/wiki/GRCroadmap.
Of course, the GRC team is pretty understaffed, and could probably take
on a couple more volunteers *cough cough*.
Cheers,
M
On 01.11.2014 18:49, Achilleas Anastasopoulos wrote:
I recently had a problem with GRC where two threads were accessing
a set_variable callback creating some unwanted behaviour
(actually crashing the xmlrpc server).
I fixed it by editing the python file created by GRC and locking the
set_ callback.
I thought that this can be a separate and interesting feature of the
"variable" block in GRC, ie, a selector that selects if the user wants
it to be "protected".
Then a piece of code like below will be generated:
self.lock = threading.Lock()
def set_variable(self, value):
self.lock.acquire()
self.value = value
other set_ cllabacks
self.lock.release()
best,
Achilleas
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
