I have an admittedly large number of blocks in my current flow graph
because I’m in the middle of some hardcore debugging. Every time I
block to enable/disable it, there is a > 2 second delay between the
becoming enabled/disabled and hitting the E/D keys. The same is true
connecting new ports together with wires. I’ve been working with this
while, but it’s annoying enough now that I’d like to know if there is a
workaround to this or simply understand the cause of it?
I had this problem for a while when using a large number of blocks. The
cause, I think, is that the companion checks if the flowgraph is correct
after every change. You will only be able to compile if it’s correct
(blocks are connected, variable names exist…).
If this is really the reason, It would be nice to have an icon that,
unselected disables this check and when selected it checks the flowgraph
and enables the compile and run options if everything is ok.
No I’m not using an embedded system to develop on. I’m using an HP Core
laptop with 16Gig of RAM, Ubuntu 14.04 with GNU Radio 3.7.8.
The delay also occurs everytime I want to make a change to a blocks
paramters. I have to wait >2 seconds for the blocks paramter window to
and then another >2 seconds for it to close. It all adds up. If the
is what Murray said, I would agree it would be nice to have the option
checking only when you click the play button or something similar.
so, I timed the flowgrah update steps rewrite, validate, create labels,
create shapes and it turns out most time is actually spent in validate.
However, for some reason the validate step currently performs the
evaluation of the params and this is also where it spends almost all of
its time. So, moving this to rewrite and making validate optional is
certainly possible, but doesn’t help (because then validate takes no
time to run). Further profiling is required.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.