Version: Unbekannt (using KDE 3.1.1) Installed from: SuSE Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB While using context-menues in konqueror or on the desktop it often happens, that at mouse-click-off an unwanted activity starts. The hot-spot of the courser is obviously inside the context-menue at this moment. Very hard, if you don't see what happens. I accidental found my diploma in the trash-dir, because I hit that menue-item. I think its a problem of the menue-position or that there is no neutral zone as a frame around the menue, that prevents the problem. Thanks for your efforts Sebastian
I never seen that. That would be a general Qt bug. What is your setup? Anything special? Did you had this problem with other versions too?
Subject: Re: contextmenues in konqueror and on desktop start unwanted activites Im using SUSE 8.2, KDE 3.11, Keramik-Stile. (for further information send detailed questions) The problem occurs a thousand times a day, almost on the Desktop and in Konqueror (big symbol viewmode). Try clicking with the right mouse-button several times on a symbol (document, folder, ...): almost the menue opens up- or downside and left- or rightside from the hotspot of the mouse-button,depending on the position of the symbol on the desktop. But sometimes (ever 3rd or 4th) the menue opens under the mousecursor. When you click-off in this situation (normaly you do - click, clack), the 'choosen' action starts. Another variant is, that the menue opens and you wiggle the mouse just a pixle, e.g. the menue is below the cursor you open your document or create a new folder. Dein / Ihr Schreiben vom Freitag, 31. Oktober 2003 13:10: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=66957 > > > > > ------- Additional Comments From coolo@kde.org 2003-10-31 13:10 ------- > I never seen that. That would be a general Qt bug. What is your setup? > Anything special? Did you had this problem with other versions too?
Subject: Re: contextmenues in konqueror and on desktop start unwanted activites Am Freitag 31 Oktober 2003 15:48 schrieb Sebastian Kenn: > Im using SUSE 8.2, KDE 3.11, Keramik-Stile. (for further information send > detailed questions) Well, my questions go more in the direction: any special time outs you set in kcontrol, is your mouse broken, do you notice such problems in gtk apps too or in pure Qt apps. Greetings, Stephan
Subject: Re: contextmenues in konqueror and on desktop start unwanted activites Dein / Ihr Schreiben vom Freitag, 31. Oktober 2003 19:03: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=66957 > > > > > ------- Additional Comments From coolo@kde.org 2003-10-31 19:03 ------- > Subject: Re: contextmenues in konqueror and on desktop start unwanted > activites > > Am Freitag 31 Oktober 2003 15:48 schrieb Sebastian Kenn: > > Im using SUSE 8.2, KDE 3.11, Keramik-Stile. (for further information send > > detailed questions) > > Well, my questions go more in the direction: any special time outs you set > in kcontrol, is your mouse broken, do you notice such problems in gtk apps > too or in pure Qt apps. > > Greetings, Stephan Hey Stephan, 1. I can't remember any special settings in kcontrol 2. My mouse is healthy - no problems otherwise 3. the problems occour in konqueror (big-symbol viewmode) and on the desktop To illustrate the trouble, I send some screenshots (hope you have a thick cable): 1. My desktop: Please pay attention to the oOO-icon in the right column 'Walking through.sxw' 2. contextmenue ok: here the menu for the document opens in the right way. It opens to the lower left side of the mouse-coursor. Nothing happens on mouse-click-off 3. contextmenue wrong: here the menu for the document opens in the wrong way. It opens to the down side of the mouse-coursor. The courser is on the top in the middle of the menue. On mouse-click-off the document starts with oOO. My idea: 'open' is the first entry in the menu and the coursor got in contact with it. Problem: I can't prevent this behavior, sometimes it happens or not. I hope to be helpfull, Sebastian PS: Kannst Du deutsch? Created an attachment (id=2950) contextmenue 1 my desktop.jpg Created an attachment (id=2951) contextmenue 2 ok.jpg Created an attachment (id=2952) contextmenue 3 wrong.jpg
Does it actually position the menu under the button? This may be same issue as in bug #76324 (I can't reproduce your report here)
Am Mittwoch, 26. Mai 2004 23:30 schrieben Sie / schriebst Du: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=66957 > > > > > ------- Additional Comments From maksim kde org 2004-05-26 23:30 ------- > Does it actually position the menu under the button? This may be same issue > as in bug #76324 (I can't reproduce your report here) Hello, I updated my system, so i can't say anything to this error. Sorry, Sebastian
Presuming it's the same then, as the most likely explanation, and lacking better information *** This bug has been marked as a duplicate of 76324 ***
Git commit 0550d4dee1769984a77c12b879e621feb3fd3ac3 by Michel Ludwig. Committed on 20/12/2011 at 22:16. Pushed by mludwig into branch 'master'. Be more cautious in 'KileDocManager::projectCloseAll'. As the list 'm_projects' will be modified by 'projectClose', we cannot use iterators to walk through the list. Patch by Eugene Shalygin. CCBUG: 66957 M +2 -2 src/kiledocmanager.cpp http://commits.kde.org/kile/0550d4dee1769984a77c12b879e621feb3fd3ac3
Git commit fd907d27dbced726d794bf24b887041eea9fbcab by Michel Ludwig. Committed on 20/12/2011 at 22:16. Pushed by mludwig into branch '2.1'. Be more cautious in 'KileDocManager::projectCloseAll'. As the list 'm_projects' will be modified by 'projectClose', we cannot use iterators to walk through the list. Patch by Eugene Shalygin. CCBUG: 66957 M +2 -2 src/kiledocmanager.cpp http://commits.kde.org/kile/fd907d27dbced726d794bf24b887041eea9fbcab
Please ignore the two comments above. They were intended for bug 289458...