Bug 70282 - editor does not scroll with page-up/down keys, works when mouse operates slider
Summary: editor does not scroll with page-up/down keys, works when mouse operates slider
Status: RESOLVED FIXED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kmdi (show other bugs)
Version: SVN
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
: 70315 74636 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-12-13 11:27 UTC by matze
Modified: 2004-03-25 14:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description matze 2003-12-13 11:27:04 UTC
Version:           CVS from 13.12.2003 (using KDE KDE 3.1.4)
Installed from:    SuSE RPMs
Compiler:          gcc 3.3.1 
OS:          Linux

when using pageup/down keys to scroll the source code, only the slider is being moved, the text stays in position. Scrolling works as usual when operating the slider with the mouse.
Comment 1 Jens Dagerbo 2003-12-13 15:40:45 UTC
Yes, and I have also seen it in kate. I not sure, but I suspect this is a kmdi problem.

Reassigning.
Comment 2 Jens Dagerbo 2004-01-12 00:02:29 UTC
*** Bug 70315 has been marked as a duplicate of this bug. ***
Comment 3 Jens Dagerbo 2004-02-09 08:36:49 UTC
*** Bug 74636 has been marked as a duplicate of this bug. ***
Comment 4 Dominik Haumann 2004-02-25 15:04:32 UTC
Some more details:
- This happens only in IDEAl mode (kate and kdevelop)
- it only happens if a sidebar tab is opened (sticky or not sticky).

regarding to kdevelop:
- if you choose QT Editor the scrollbar gets focus, too, BUT it is possible to scroll up/down.

It's probably a KMDI thing
-- imho the kate/katepart behaviour is ok, because the scrollbar should _never_ have focus (because then I would have to click into my source code _again_ to be able to go on writing :( )
Comment 5 Dominik Haumann 2004-02-25 15:10:11 UTC
imho the kate/katepart behaviour is ok, because the scrollbar should _never_ have focus (because then I would have to click into my source code _again_ to be able to go on writing :( )
Comment 6 Jens Dagerbo 2004-03-25 14:19:47 UTC
CVS commit by dagerbo: 

Clever workarounds that cause more problems than they solve are a Bad Idea (tm)

CCMAIL: 70282-done@bugs.kde.org


  M +5 -3      kmdimainfrm.cpp   1.59


--- kdelibs/kmdi/kmdimainfrm.cpp  #1.58:1.59
@@ -2492,7 +2492,7 @@ void KMdiMainFrm::setActiveToolDock(KMdi
     if (d->activeDockPriority[0]==0) {
         d->activeDockPriority[0]=td;
-        d->focusList=new KMdiFocusList(this);
-        if (m_pMdi)  d->focusList->addWidgetTree(m_pMdi);
-        if (m_documentTabWidget) d->focusList->addWidgetTree(m_documentTabWidget);
+//        d->focusList=new KMdiFocusList(this);
+//        if (m_pMdi)  d->focusList->addWidgetTree(m_pMdi);
+//        if (m_documentTabWidget) d->focusList->addWidgetTree(m_documentTabWidget);
         return;
     }
@@ -2515,4 +2515,5 @@ void KMdiMainFrm::removeFromActiveDockLi
         }
     }
+/*    
     if (d->activeDockPriority[0]==0) {
         if (d->focusList) d->focusList->restore();
@@ -2520,4 +2521,5 @@ void KMdiMainFrm::removeFromActiveDockLi
         d->focusList=0;
     }
+*/    
 }