That was happening because you still have one installation of your OOT lingering around somewhere, and you're installing your new version in a different place that Python/GRC doesn't look.
You'll want to fix both issues: * uninstall all copies of your OOT module * install your OOT module so that the YAML files end up where GRC actually looks Best regards, Marcus On 23.10.20 21:41, Mirelle DeSpain wrote: > I don’t know what changed, but I fixed it in the most asinine way possible: > copying the same files to a new block and then it magically worked. > > I no longer need help, thank you. > >> On Oct 23, 2020, at 11:40 AM, Mirelle DeSpain <[email protected]> wrote: >> >> >> I have a custom GNU Radio block. It was working well before we uninstalled >> and reinstalled GNU Radio. Now it seems to be stuck on the previous >> configuration. I edited the YML to remove a parameter, but even after >> building my OOT module and refreshing GRC, it still appears. >> >> I did some research and we found that the block path is >> "/usr/local/share/gnuradio/grc/blocks" based on the GRC startup. If I look >> in this location, I find my new YML, which doesn't contain the removed >> parameter, yet it still appears in the GRC block. >> >> Here's the YML block in the block path. >> <YML_screenshot.png> >> >> Here's the parameter still showing up in GRC. >> <Param.png> >> >> >> Has anyone else had this problem before? Any hints on what to check or how >> to fix it? >
