Instead of discussing this further in scarab I'm moving it to this mailing list where I should have started it all. ;)
From: Mick Semb Wever [mailto:[EMAIL PROTECTED] > > *[JIRA] Bug SKER4755 - currentTab is set to the tab's parent-key instead of > > key* > > Scarab Link: http://sesat.no/scarab/issues/id/SKER4755 > > This is an old issue and is the original intended functionality. > Nothing can be 'fixed' so to speak here. > Read SKER1620 comments for example. > > The intended functionality is such that parent-key is used when > you want a tab to basically pretend to be another tab > (eg links point to etc) but you are infact a sub tab of. > These are 'hidden' keys so to speak. > > If you really want SearchTab.getKey() to return the true key, > move this issue to an improvement and to 2.18. Otherwise i will close to Wont > fix. I feel this should be discussed further before any action is taken. While I see that it could be useful to be able to get the "main" tab (parent-tab), it still should be possible to get the true key. What about a getKey() that works as it does today and a getTrueKey()/getRealKey()/whatever that ignores the parent-key attribute? -- Magne _______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
