But of course you can highlight them and search the rest of the function for related entries. This at least lets you track down if/how they are called..
But of course you can highlight them and search the rest of the function for related entries. This at least lets you track down if/how they are called..
Dont forget that if your code consists of multiple function files, that you need to ensure IGOR searches all the relevant .ipf's and not just the current file.
Dont forget that if your code consists of multiple function files, that you need to ensure IGOR searches all the relevant .ipf's and not just the current file.
Thanks, yeah I know. I was mainly interested in doing this for a function's local variables as I've got several projects where I'm combining multiple procedure functions from someone else's rather crude coding (they used a lot of randomly placed variable and string declarations in rather lengthy functions). It would have been nice to have something flag all the unused ones automatically; however, I can copy each function to a separate procedure file and then do a search on each variable I find to clean them up. Cumbersome, but doable.
April 4, 2013 at 09:20 pm - Permalink
April 5, 2013 at 03:43 am - Permalink
April 5, 2013 at 05:46 am - Permalink
Ah, why didn't I think of that. :D
April 5, 2013 at 10:26 am - Permalink
April 6, 2013 at 02:49 am - Permalink
Thanks, yeah I know. I was mainly interested in doing this for a function's local variables as I've got several projects where I'm combining multiple procedure functions from someone else's rather crude coding (they used a lot of randomly placed variable and string declarations in rather lengthy functions). It would have been nice to have something flag all the unused ones automatically; however, I can copy each function to a separate procedure file and then do a search on each variable I find to clean them up. Cumbersome, but doable.
April 6, 2013 at 09:01 am - Permalink