|
|
> Thanks, Wayne, for your answers to my recent questions about saving
> and opening ROI files. One of your answers explained how one might
> write a macro for creating and manipulating ROIs in a text editor. In
> playing with the RoiManager I noticed that the macro recorder could
> record some buttons but not others (e.g. Rename). I'd like to be able
> to record all RoiManager button events, and this brings me to a new
> area of curiosity.
Starting with ImageJ 1.37h, clicks in the ROI Manager list and on the
"Rename" button are recorded. The recorder generates code that looks
like this:
roiManager("Select", 1);
roiManager("Rename", "A new name");
> Rather than just add to an increasing number of feature requests (so
> growing because as ImageJ increases in capability, new possibilities
> arise!), how can ImageJ users help get such features implemented?
> Would submission of proposed source code fragments help, or would this
> bog you down in having to orient to and check code not of your own
> design?
I like getting code submissions. It's best if the proposed feature has
wide appeal and that any changes to existing code are limited and well
marked.
-wayne
|
Locked
