hi,
Thanks for your patient explaianation.
I am glad to make the request, and it is done:
https://github.com/gnuradio/gnuradio/issues/6458
BTW, would you pls consider changing the GRC like this:
- name: epy_block_0
id: epy_block
parameters:
/* _source_file: "epy_block.py"*/
affinity: ''
alias: ''
comment: ''
maxoutbuf: '0'
minoutbuf: '0'
vectorSize: vectorLength
At this time, the editor issue doesnot exist any more. epy_block.py is
located under working directory (or any directory on the disk), anyone
can edit the epy file with his favorite editor. And the coupling degree
of the GRC decreases.
Thanks.
在 2023/1/9 19:24, Marcus Müller 写道:
Hi,
On 09.01.23 03:14, wieniawski wrote:
1. the local([working dir])'s conf file has the information that it
will override the setting in ~/.gnuradio/config.conf
No, it's not even read. As I wrote!
GNU Radio does not *care* about config files outside ~/.gnuradio.
And that is, in my opinion, a good thing, honestly. There's way too
many surprised to be had if the behaviour of a GUI program depended on
from where it was started.
2. I tried to change local_blocks_path = ./, which works. block
python file will be generated under working directory.
No. local_blocks_path has no effect whatsoever on where blocks are
generated.
It's just one of the paths that GRC **looks** into to **find** blocks.
eh...., so the only way to find out how to edit conf file is this
email list?
Sadly: Yes, that or reading the code. :(
Generally, as a project we don't have *that* many things that are
configurable, and those that are often things you would tend to avoid
letting users do by hand. I consider the fact that there's no way to
comfortable change the editor setting from GRC a usability bug, in all
honesty.
Would you care to help us, by making a "Feature Request" on
https://github.com/gnuradio/gnuradio/issues/new/choose
that basically says "I want to change the editor in a way that is
easy, from within GRC"?
Best regards,
Marcus
