From 30a0b24150f8bf41e463f5f72f2ae9609ea1eadb Mon Sep 17 00:00:00 2001 From: Kevin Day Date: Fri, 30 Oct 2020 20:25:41 -0500 Subject: [PATCH] Bugfix: FSS Extended List did not actually record parent path, prevented nests from being processable. It seems that I completely forgot to actually save the parent location. Without this there is no way to map one nested item to its parent. --- level_1/fl_fss/c/fss_extended_list.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/level_1/fl_fss/c/fss_extended_list.c b/level_1/fl_fss/c/fss_extended_list.c index 6743784..fd3c93d 100644 --- a/level_1/fl_fss/c/fss_extended_list.c +++ b/level_1/fl_fss/c/fss_extended_list.c @@ -660,8 +660,10 @@ extern "C" { if (F_status_is_error(status)) break; } - // only assign object positions for nested objects. - if (depth > 0) { + if (depth) { + found->depth[depth].array[position].parent = found->depth[depth - 1].used; + + // only assign object positions for nested objects. found->depth[depth].array[position].object.start = objects.array[depth].start; found->depth[depth].array[position].object.stop = objects.array[depth].stop; } -- 1.8.3.1