Bio7 3.3 on MacBook Pro M1


Recently I tested Bio7 3.3 on MacBook Pro M1. The application runs fine with Rosetta (you will be asked for if not installed).

Important note for R:

To run R with Bio7 interestingly you have to install R for Intel (again runs on Rosetta) and then Rserve from Github (as explained in the manual).

With this setup I experienced no problem so far.

R Editor and ImageJ Plugin Update


Two new plugin updates are available for Bio7.

R Editor update:

The R editor plugin has been updated for the new R 4.1 grammar (shorthand function notation, native pipe operators). The new grammar is also considered in the code completion of the editor and in the R-Shell (e.g., function calls, pipes with piped dataframes).

Annonymous shorthand functions are also displayed as ‘aFunc’ in the Outline view.

ImageJ Plugin update:

  1. Improved the ‘Detach Images’ menu action
  2. Added an post activation action for detached views (‘Open All Images as Views’ action bugfix for Windows)
  3. Improved the layout action for orthogonal stack views (in detached views)
  4. Added an API method to invoke the ‘Open All Images as Views’ action
  5. The ImageJ macro action ‘setLocation’ will now change the size and location of detached views if available
  6. Fixed some minor bugs

For the R editor update add the following URL site to the Update Manager:

For ImageJ (if not already available) add:


Fixed OpenJDK Path for MacOSX – Allow Bio7 on Big Sur


Uploaded MacOSX version with corrected OpenJDK path

In the latest MacOSX release the path to the embedded Java OpenJDK was wrong (not a relative path). I uploaded a corrected version to sourceforge.

If you have already downloaded Bio7 you can simply correct the path in the Bio7.ini file (right-click, “Show Package Contents”, Path: “Contents/Eclipse”. Replace the vm path argument with the relative path to the embedded OpenJDK:


Fix – can’t run app because of permission in Big Sur

If you can’t open Bio7 after download even after the changes of the security settings try the following command-line recipe:

Solution which worked in the Terminal:

> sudo chmod -R 755 /Applications/

> sudo xattr -dr /Applications/

There is also a utility app available on Github to help with the MacOSX security settings, see: