Martijn Jasperse

Thanks for the report. The bug was fixed in commit [720f2a] and is included in release v2.15.0

I had another go at updating the permissions - hopefully you can create a ticket now, although I will look towards migrating to github at some point soon. Feel free to shoot me an email to arrange a chat; m-dot-jasperse-at-gmail-dot-com. My timezone is AEST which can be awkward depending on where you are, but we can probably find something that works. Cheers, Martijn

Hi, It should not be necessary to include the EXT and LIB files - those are build artifacts and are not used by LabVIEW. However when you say "the two HDF5-related DLLs" that is not correct; you require ALL the distributed DLLs for the target architecture. They are required to be separate files per their licensing conditions, which is why there are several of them. Unfortunately Windows itself does not provide any diagnostic information when failing to load a DLL - it just reports "failed" and does...

Hi Paul, Sorry again for missing this - thanks for the descriptive scenario; it's not something I had considered myself previously. The dimensionality restriction was originally applied for sanity-checking in the C library because there was a lot of complexity on the LV side for higher-dimensional arrays. The implementation means you can always perform a read as either a "flat" 1D array (irrespective of the stored dimensionality), or as an array of equal dimension to the stored array. So for this...

Hi Paul, Very sorry I never noticed your forum posts; I had just changed jobs in May and I guess I completely lost track of my inbox. Thanks for reporting that issue with the datatype. Probably my preference would be to raise a ticket in SF, although it's a bit clunky. Did you end up forking in-house? Would be very happy to upstream any fixes or improvements you made, although in the past there have been issues due to my ancient LV2010 edition and my preference to continue to support older LV editions,...

Thanks for the kind words about this project, always nice to hear that my work has been useful to someone! It's been a long time since I worked on this project - is that call to H5LVget_variant_dims() part of one of the library VIs or is it part of your code? Edit: Sorry, I missed that you mentioned it's H5Dappend.vi. I think probably it makes sense to try to detect this scenario and skip the dataset operations since that just wasted CPU cycles LabVIEW represents "empty" arrays in several possible...

Thanks for the kind words about this project, always nice to hear that my work has been useful to someone! It's been a long time since I worked on this project - is that call to H5LVget_variant_dims() part of one of the library VIs or is it part of your code? LabVIEW represents "empty" arrays in several possible ways - one of which is to pass around a NULL pointer as a placeholder. So sometimes code breaks on empty arrays because it expected a valid pointer and got NULL, which is a hard-fault condition....

Hi, Apologies for the late reply as I was on vacation. I guess I forgot to update the CHANGES file, so I've gone back and updated it now. There is an updated version in both the repo and attached to this post. The primary change was updating from HDF5 v1.8.X to v1.10.X and exposing some of the new functionality that was made available in that version. Additional bug fixes are listed are listed in the file. Cheers, Martijn