Bug #124

Tree Model / Tree View

Added by fba about 1 year ago. Updated 12 months ago.

Status:Assigned Start date:19 Jun 2011
Priority:High Due date:26 Jun 2011
Assignee:rbe % Done:

80%
Category:graphical interface
Target version:1.2

Description

When two folders (or more) at the same level have the same name the Tree View does not create another entry but adds contents of each folder under the same parent. For example, two folders with the same name. The first one has a subfolder named SubFolder1 and the second one has a subfolder SubFolder2, the TreeView will provide the following hierarchy:

-- Folder
    |-- SubFolder1
    |-- SubFolder2

instead of having

|-- Folder
|    |-- SubFolder1
|-- Folder
     |-- SubFolder2

It seems that in some situtations, content is not added at all.

Related issues

follows (30 days) Digital Forensics Framework - Development #131: Nodes formal identifier New 19 May 2011

History

#1
Updated by rbe about 1 year ago

  • Target version set to 1.1

#2
Updated by rbe about 1 year ago

It seems that this bug, and all related issues on the nodes display on the tree view, comes from the fact that node's names are used as identifier.

Problems occur when several nodes have the same name. The model associated with the tree view should use node.this or node.id() (which are unique) as formal identifiers.

#3
Updated by rbe about 1 year ago

  • % Done changed from 0 to 50

#4
Updated by rbe about 1 year ago

  • % Done changed from 50 to 80

#5
Updated by rbe 12 months ago

This issue cannot be properly fixed for now without modifying the API in depth. Indeed, a lot of the framework components use the method Node * VFS::GetNode(std::string node_name), returning a pointer to a Node according to the a node name.

As some nodes can have the same name (such as deleted data), the GetNode method returns a pointer to ONE of these nodes, which is likely not to be the one the caller expected. It implies that in the GUI, some nodes are sometimes added in the wrong father.

Getting rid of this behavior implies that the API and modules do not use the GetNode method anymore and prefer using the Node.id() method. This functionality is still in an experimental stage for now and cannot be safely integrated in the next release.

I am closing this issue, and creating an other one :
https://tracker.digital-forensic.org/issues/131

Once it is fixed, this issue can be reopened.

#6
Updated by rbe 12 months ago

  • Status changed from New to Assigned
  • Target version changed from 1.1 to 1.2

Also available in: Atom PDF