On 1/13/2017 3:36 AM, Thomas Baumgart wrote:
Thanks for the detailed analysis. I think it hits the nail right on the head.
Date and timezone handling is all done by libOFX (I fixed something myself in
that are sometime ago - wow 7 years:
https://github.com/libofx/libofx/commit/166b97964de3ed39863
On 10/4/2016 4:43 PM, Jack wrote:
> On 2016.10.04 15:49, jef...@outlook.com wrote:
>> On October 4, 2016 4:07 PM, Jack wrote:
>>
>> >On 2016.10.03 02:20, Thomas Baumgart wrote:
>> >> On Monday 03 October 2016 02:33:49 jef...@outlook.com wrote:
>> >>
On October 4, 2016 4:07 PM, Jack wrote:
>On 2016.10.03 02:20, Thomas Baumgart wrote:
>> On Monday 03 October 2016 02:33:49 jef...@outlook.com wrote:
>>
>>> On Sunday, October 2, 2016 9:31 PM, Jack wrote: I could see the
>>> clientuid box on the ofx details
On Sunday, October 2, 2016 9:31 PM, Jack wrote:
> I could see the clientuid box on the ofx details page, I couldn't enter
> anything
If the box cannot be edited, it seems that the KMM build did not recognize that
libofx supports CLIENTUID, and so disabled the box. And if that's true, then
eve
