Miguel Agueda

I just tried the new development version and all the test images I sent work as expected. I will try some other images later, and I'll let you know if I encounter any bugs.

I've done some testing as well in WSxM and, as far as I can tell, the behavior in WSxM depends on the Image Data Type. If the image contains integer values, it will take the range of values in the image and map it to the Z Amplitude. On the other hand, if the image contains floating point values, it would completely ignore the value provided, and just use the units provided with the raw values. Here I attach some example images I've generated in Matlab, using both integer and floating point.

Thank you for the improvements. Could you point me to a description on how the Z Amplitude is typically handled on this files? I'm not aware of any documentation of how this files are structured. I might be able to programmatically add/modify the information on the header to make them behave as expected. Thanks in advance

Dear all, I'm having some issues opening some .stp files. I have reproduced this issue in multiple platforms (both in macOS and Windows 10 using the version 2.65 of the software). The files were generated using a third party program, but they can be read in WSxM just fine. I attach an example image, as well as the resulting data I get when loading into WSxM. The header info is quite sparse, but it always the same structure. Let me know if any extra information is required. Thank you, Miguel

Copy/paste and undo/do icons missing

I've tried to build Scidavis from source using cmake, following your guidelines to use qwt and qwtplot3d git submodules. Aside from not being able to build python scripting ( because I haven't figured out how to get the PyQt dependencies), everything builds perfectly on Fedora 33, and all the unittest run succesfully.

Thank you for the update. I'm glad to see so much progress and wider compatibility. I imagine that the Windows build issues are the main blocker for a new release, if nothing else comes up. Given the new build system, it should also be easier to build on more linux distros. Regarding doing builds from source on linux, is the procedure still the same, as described in github INSTALL.md ? Thank you

Great! I'm happy to hear that. I did manage to compile it myself yesterday. I couldn't do it on Fedora that I use, because I got an error about lupdate not being avaliable, but I manage to compile on Ubuntu 18.04 without python and then copy it over Fedora and link scidavis to the needed libraries on the system. It's kind of janky, and I'm not confident it'll work very well, but I can use it to export the tables. 2.3.1 would entail no source code difference between it and 2.3.0 Okay, I see what you...