Bug 470764 - JavaFX toolkit - TreeTableView - select entry by textpath leads to Action Error
Summary: JavaFX toolkit - TreeTableView - select entry by textpath leads to Action Error
Status: CLOSED DUPLICATE of bug 470706
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: RC (show other bugs)
Version: unspecified   Edit
Hardware: All Windows All
: P3 normal (vote)
Target Milestone: 4.0   Edit
Assignee: Maissmaallsmyss Maulhs-Vvuillss CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
: 470765 (view as bug list)
Depends on:
Blocks: 421595
  Show dependency tree
 
Reported: 2015-06-23 02:35 EDT by Maissmaallsmyss Maulhs-Vvuillss CLA
Modified: 2016-05-19 03:40 EDT (History)
2 users (show)

See Also:


Attachments
logs & TestResults (4.42 KB, application/zip)
2015-06-23 02:35 EDT, Maissmaallsmyss Maulhs-Vvuillss CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maissmaallsmyss Maulhs-Vvuillss CLA 2015-06-23 02:35:35 EDT
Created attachment 254621 [details]
logs & TestResults

JavaFX toolkit - TreeTableView - select entry by textpath (specify column) leads to Action Error (not found), thought the node exists. Regular expressions (e.g. .*PERS.*) does not help. 
Jubula version 8.1.4
Comment 1 Alexandra Schladebeck CLA 2015-06-23 03:08:14 EDT
Can you say:
- whether this action worked in the previous version (8.1.3)
- what the structure of the treepath is? Are you sure that the root note is PERSONENBELADUNG?
Comment 2 Alexandra Schladebeck CLA 2015-06-23 03:09:32 EDT
*** Bug 470765 has been marked as a duplicate of this bug. ***
Comment 3 Alexandra Schladebeck CLA 2015-06-23 03:13:28 EDT
Also marking this as a duplicate. If (for whatever reason) a treepath can't be found, it stands to reason that the select and the check would fail. 

Maissmaallsmyss, please let us know what the structure of the tree is - I know that we looked at selection in tree tables last week together and I'd like to rule out that the data you are entering are incorrect. 

Thanks!

*** This bug has been marked as a duplicate of bug 470706 ***