In the MenuRefresher we override ImageJ 1.x's Memory & Threads plugin. However this results in skew with the search bar.
I am not sure where the search results are produced.. I think these are LegacySearchActions? But I am not sure how what the run method is actually doing.
I think one option would be to route the search action run method to use the menu command. A more robust option would be to try and push this code to imagej-legacy and go direct bytecode manipulation of the Memory method. It would just need some abstraction to point to the scijava configuration file instead of fiji.cfg explicitly.
In the MenuRefresher we override ImageJ 1.x's
Memory & Threadsplugin. However this results in skew with the search bar.I am not sure where the search results are produced.. I think these are LegacySearchActions? But I am not sure how what the
runmethod is actually doing.I think one option would be to route the search action
runmethod to use the menu command. A more robust option would be to try and push this code toimagej-legacyand go direct bytecode manipulation of theMemorymethod. It would just need some abstraction to point to the scijava configuration file instead offiji.cfgexplicitly.