Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script editor autocompletion for "exit" #218

Closed
miura opened this issue May 9, 2019 · 3 comments
Closed

Script editor autocompletion for "exit" #218

miura opened this issue May 9, 2019 · 3 comments

Comments

@miura
Copy link
Member

miura commented May 9, 2019

Autocompletion in the scritpt editor for the function "exit" has a small bug. See the image below.

image

@ctrueden
Copy link
Member

ctrueden commented May 9, 2019

Looking at the functions.html, it appears that this exit function is the only one that has multiple invocations separated by an or outside the parentheses.

@haesleinhuepf Our priority should be to make sure that functions.html works as written automatically without tweaking, right? So that we can easily keep it updated as time goes on by dropping in new versions? If so, we need to write some special-case parsing for this odd case, right?

@rasband
Copy link
Member

rasband commented May 9, 2019

I updated the file at
http://wsr.imagej.net/developer/macro/functions.html

so that exit and exit("error message") are separate entries.

<a name=exit></a>
<b>exit</b><br>
Terminates execution of the macro. 
<p>

<b>exit("error message")</b><br>
Terminates execution of the macro and displays an error message. 
<p>

@rasband rasband closed this as completed May 9, 2019
@ctrueden
Copy link
Member

@haesleinhuepf I tried to update the locally bundled functions.html resource to finish addressing this issue, but it seems there are many differences between the local copy and the one on the remote site. So I wasn’t sure what the process is for updating it? Did you make modifications manually? If so, do you have automation to remake them when things change? And can we commit that script to the repo? Or if not: would it make sense to create such a script?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants