i have a annoying problem with the GRC workspace. this happens:
i write my own GRC wrapper for same Blockes and place them with the
tag in a own category. (Note: i dont adjust the Block tree
init
files ). All blocks wrapped correct and works fine.
Now when i have only same std. Grc Blocks in the workspace, all blocks
can
be moved. but if i put one of my blocks in there,no block can be moved,
also
the std. Blocks. but note all blocks works fine anyway in the grc
flowgraf.
Second Problem: yesterday all works well and i could move all blocks:-(
i start grc in a terminal and i cant see any error
someone has the same problem?
Ps.: i worked on a VM using Ubuntu 10.4 and a Gnuradio release from nov.
2011
Sounds like it’s an install problem. When building, does gr-digital
build?
And make sure to do a ‘make install’. Also, if you are installing it to
a
non-default prefix, make sure PYTHONPATH is pointing to the right
directory.
to finish the problem, here my results i figured out:
how i descriped this happens cause an invalid import tag in wrapper
files.
in my case this was “from gnuradio import digital” because i import in
the
digital init File a module that include stuff from the mayavi
visualization framework. ok…
the residual Question for me is, why its not working, because in Python
shell i can import this stuff without errors(GRC too, but with the
problem
of fixed workspace) and run Apps without warnings etc.
i used >>python -v to tracking the import of mayavi stuff and the only
think
i filtert out that could be a problem are things like “bad mtime”
warnings.
Additonal mayavi includes many modules, so can this be a reason too.
It will be cool if sombody can force this too and verify the behavior