Return-Path: X-Original-To: apmail-flex-issues-archive@minotaur.apache.org Delivered-To: apmail-flex-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DCEB31105A for ; Mon, 21 Jul 2014 14:12:45 +0000 (UTC) Received: (qmail 96357 invoked by uid 500); 21 Jul 2014 14:12:45 -0000 Delivered-To: apmail-flex-issues-archive@flex.apache.org Received: (qmail 96334 invoked by uid 500); 21 Jul 2014 14:12:45 -0000 Mailing-List: contact issues-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list issues@flex.apache.org Received: (qmail 96321 invoked by uid 99); 21 Jul 2014 14:12:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jul 2014 14:12:45 +0000 Date: Mon, 21 Jul 2014 14:12:45 +0000 (UTC) From: "Mihai Chira (JIRA)" To: issues@flex.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLEX-34424) HierarchicalCollectionViewCursor.current returns null when last item of current level selected and previous sibling is removed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLEX-34424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mihai Chira updated FLEX-34424: ------------------------------- Description: I'm about to commit a unit test which uncovers this bug. Until then, brief steps to reproduce: # Create a HierarchicalCollectionView with a hierarchical structure with at least 2 levels of depth. See structure at the end of the ticket for example. # Create a HierarchicalCollectionViewCursor via HierarchicalCollectionView.createCursor(). # Call HierarchicalCollectionViewCursor.seek(11), which (correctly) makes HierarchicalCollectionViewCursor.current == "Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(3)" # Remove "Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(1)" from its collection *Actual behaviour*: HierarchicalCollectionViewCursor.current becomes null. *Desired behaviour*: HierarchicalCollectionViewCursor.current stays "Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(3)". *Example structure*: Region(1) Region(2) Region(2) -> City(1) Region(2) -> City(1) -> Company(1) Region(2) -> City(1) -> Company(2) Region(2) -> City(1) -> Company(2) -> Department(1) Region(2) -> City(1) -> Company(2) -> Department(1) -> Employee(1) Region(2) -> City(1) -> Company(2) -> Department(1) -> Employee(2) Region(2) -> City(1) -> Company(2) -> Department(2) Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(1) Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(2) Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(3) Region(2) -> City(1) -> Company(2) -> Department(3) Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(1) Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(2) Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(3) Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(4) Region(2) -> City(1) -> Company(3) was: I'm about to commit a unit test which uncovers this bug. Until then, brief steps to reproduce: # Create a HierarchicalCollectionView with a hierarchical structure with at least 2 levels of depth. See structure at the end of the ticket for example. # Create a HierarchicalCollectionViewCursor via HierarchicalCollectionView.createCursor(). # Call HierarchicalCollectionViewCursor.seek(11), which makes HierarchicalCollectionViewCursor.current == "Region(2)->City(1)->Company(2)->Department(2)->Employee(3)" # Remove "Region(2)->City(1)->Company(2)->Department(2)->Employee(1)" from its collection *Actual behaviour*: HierarchicalCollectionViewCursor.current becomes null. *Desired behaviour*: HierarchicalCollectionViewCursor.current stays "Region(2)->City(1)->Company(2)->Department(2)->Employee(3)". *Example structure*: Region(1) Region(2) Region(2) -> City(1) Region(2) -> City(1) -> Company(1) Region(2) -> City(1) -> Company(2) Region(2) -> City(1) -> Company(2) -> Department(1) Region(2) -> City(1) -> Company(2) -> Department(1) -> Employee(1) Region(2) -> City(1) -> Company(2) -> Department(1) -> Employee(2) Region(2) -> City(1) -> Company(2) -> Department(2) Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(1) Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(2) Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(3) Region(2) -> City(1) -> Company(2) -> Department(3) Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(1) Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(2) Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(3) Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(4) Region(2) -> City(1) -> Company(3) > HierarchicalCollectionViewCursor.current returns null when last item of current level selected and previous sibling is removed > ------------------------------------------------------------------------------------------------------------------------------ > > Key: FLEX-34424 > URL: https://issues.apache.org/jira/browse/FLEX-34424 > Project: Apache Flex > Issue Type: Bug > Components: Advanced Data Grid, mx: Tree > Affects Versions: Apache Flex 4.12.1 > Reporter: Mihai Chira > Assignee: Mihai Chira > > I'm about to commit a unit test which uncovers this bug. Until then, brief steps to reproduce: > # Create a HierarchicalCollectionView with a hierarchical structure with at least 2 levels of depth. See structure at the end of the ticket for example. > # Create a HierarchicalCollectionViewCursor via HierarchicalCollectionView.createCursor(). > # Call HierarchicalCollectionViewCursor.seek(11), which (correctly) makes HierarchicalCollectionViewCursor.current == "Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(3)" > # Remove "Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(1)" from its collection > *Actual behaviour*: HierarchicalCollectionViewCursor.current becomes null. > *Desired behaviour*: HierarchicalCollectionViewCursor.current stays "Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(3)". > *Example structure*: > Region(1) > Region(2) > Region(2) -> City(1) > Region(2) -> City(1) -> Company(1) > Region(2) -> City(1) -> Company(2) > Region(2) -> City(1) -> Company(2) -> Department(1) > Region(2) -> City(1) -> Company(2) -> Department(1) -> Employee(1) > Region(2) -> City(1) -> Company(2) -> Department(1) -> Employee(2) > Region(2) -> City(1) -> Company(2) -> Department(2) > Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(1) > Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(2) > Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(3) > Region(2) -> City(1) -> Company(2) -> Department(3) > Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(1) > Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(2) > Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(3) > Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(4) > Region(2) -> City(1) -> Company(3) -- This message was sent by Atlassian JIRA (v6.2#6252)