Skip to content

DataTree Sync Browsing: Rationale behind copy of only currElem #4

@sstucker

Description

@sstucker

Hi,

I'd like to talk about the implementation of the SyncBrowsing feature: why is only the current element copied to locDataTree2 and pointed to by dataTreeHandle --depending (I think) on the sync browsing paramater-- when the entire tree is always copied at locDataTree regardless?

image

Above is the relevant code in SyncBrowsing.m

@jayd1860

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions