Desirable "compile and run" change

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Desirable "compile and run" change

David Webster
All,

I would like to suggest a change to the way that
"compile and run" works. It would make more sense
to me to have "compile and run" apply specifically
to the code that has been opened by the plugin command
or the editor. This as opposed to running what ever is
installed in the pluginslist regardless of what may have
been compiled. Thisseems to be more in keeping with what
one would intend to happen when opening a file.

David Webster

P.S. The plugins menu command does not have an edit option as
is implied by the documentation, one must go to the macros option.
Reply | Threaded
Open this post in threaded view
|

Re: Desirable "compile and run" change

Gabriel Landini
On Tuesday 21 July 2009  09:07:53 David William Webster wrote:
> I would like to suggest a change to the way that
> "compile and run" works. It would make more sense
> to me to have "compile and run" apply specifically
> to the code that has been opened by the plugin command
> or the editor.

Do you mean the "File>Compile and Run" in the editor window?

> This as opposed to running what ever is
> installed in the pluginslist regardless of what may have
> been compiled.

Sorry I do not understand what you meant above.

> P.S. The plugins menu command does not have an edit option as
> is implied by the documentation, one must go to the macros option.

Yes, that is the option to open a Plugin. It says "Open Macro or Plugin" in
the dialog title bar.
Or you can drag and drop the file on the IJ window.


Cheers

G.
Reply | Threaded
Open this post in threaded view
|

Re: Desirable "compile and run" change

dscho
In reply to this post by David Webster
Hi,

On Mon, 20 Jul 2009, David William Webster wrote:

> I would like to suggest a change to the way that
> "compile and run" works. It would make more sense
> to me to have "compile and run" apply specifically
> to the code that has been opened by the plugin command
> or the editor. This as opposed to running what ever is
> installed in the pluginslist regardless of what may have
> been compiled.

There was a bug in Fiji which made it display the behavior you describe,
but that was fixed in the Dresden-2009 version.

So maybe you want to be a bit more specific about what scenario you are
talking about.  Maybe you are editing a file outside of the plugins/
folder?

Ciao,
Dscho