Brice

Yes, this is a good idea I have been thinking about. It's a bit involved but will work on this. It may take a bit of time though.

Thanks for the detailed issue. I understand this issue, it has to do with the interpretation of the profile.xls, in the case of this field, it's a special type that...

do you mind if I use your example file and include it as a test case?

pushed a fix, thanks for the bug. let me know if you still have some issues

Note also that it does not really get the unit resolved, the specification for field with offset in the profile file is a bit incomplete, and I already had to...

Hum. you make a very good point. but your message got me a bit confused as to how I should deal with it :) The library attempts to interpret as...

You were right, but no longer :) I fixed it in the last commit... So for HR now: - if custom_target_heart_rate_high = 70 you will get custom_target_heart_rate_high = 70 and...

Don't worry then, it was just if easy to generate. Let me know if latest version works for you and I will close the issue

Thanks. yes it’s a proof of concept/learning tool but turned out actually useful I am actually working on improving it a bit. Especially in handling better files of different types,...

The latest code answers some of these: - it should not leave empty destination file (but possible I missed some workflow where this happens) - it now tries to keep...