excuse me Mark if I use the forum for this comunication, but your mail doesn't work.
Last week I downloaded the 2.3.0 version and I have a problem with f-k tools.
I can't find them in "file-preferences-tools" path
I can't find the f-k tools in the /bin root .
Is it a bug or mine error?
thank you for your attention
2.3.0 version and f-k tools
Hi Riccardo,
Which operating system are you running geopsy? Linux, Mac or Windows?
Under Windows, FK tools are implemented in plugin library 'geopsyarrayX.dll' (X is version number), usually in C:\Program Files\Geopsy.org\bin
Under Linux, it should be here /usr/local/Geopsy.org/lib/libgeopsyarray.so
Did you select all packages when downloading geopsy?
If you are running it under Windows, there are currently bugs in the installation software for upgrading an existing installation. This will be fixed for next minor release 2.3.1 (hopefully). Hence, the safest way is to uninstall all Geopsy.org packages from your computer (if 'uninstall.exe' fails, remove manually everything in C:\Program Files\Geopsy.org) and re-install everything.
Thanks for reporting how you solved this issue.
Marc
Which operating system are you running geopsy? Linux, Mac or Windows?
Under Windows, FK tools are implemented in plugin library 'geopsyarrayX.dll' (X is version number), usually in C:\Program Files\Geopsy.org\bin
Under Linux, it should be here /usr/local/Geopsy.org/lib/libgeopsyarray.so
Did you select all packages when downloading geopsy?
If you are running it under Windows, there are currently bugs in the installation software for upgrading an existing installation. This will be fixed for next minor release 2.3.1 (hopefully). Hence, the safest way is to uninstall all Geopsy.org packages from your computer (if 'uninstall.exe' fails, remove manually everything in C:\Program Files\Geopsy.org) and re-install everything.
Thanks for reporting how you solved this issue.
Marc
Currently working on bug fixes for the installation process, I encountered the same problem as you reported: missing geopsyarray plugin when upgrading from 2.2.1 to 2.3.0 (Windows XP). However, completely uninstalling 2.2.1 before the new installation solves the problem. The bug comes from the fact that installator is mixing source compatibility and binary compatibility. A correction is planned for the next minor release.
Meanwhile, a complete uninstall should fix the problem.
Meanwhile, a complete uninstall should fix the problem.