Bug 169884 - right-click menu problem for the dictionary widget
Summary: right-click menu problem for the dictionary widget
Status: RESOLVED UPSTREAM
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-26 21:43 UTC by renguoqin
Modified: 2008-12-23 18:35 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description renguoqin 2008-08-26 21:43:16 UTC
Version:            (using KDE 4.1.0)
OS:                FreeBSD
Installed from:    FreeBSD Ports

Add a dictionary widget. Type a word in the dictionary's searching bar, for example, "vacuum". Then right click in the searching bar. You will see the menu, but part of it is blocked by the dictionary widget.
Comment 1 Dario Andres 2008-08-27 18:23:42 UTC
Qt: 4.4.0
KDE: 4.1.1 (KDE 4.1.0 (4.1 >= 20080722))
Plasma Workspace: 0.1
in ArchLinux i686:

I can reproduce this bug
Comment 2 step247 2008-09-10 10:24:24 UTC
If I enter a word to dictionary widget and hit enter, nothing happens. Most cases I can not even enter a word to search because widget refuses to become "active". 

Dictionary widget (idiotic-sounding word or what? Say it 5 times!), menu  is hidden behind the widget and the panel. Sometimes part of the menu shows up at the top of the screen.

Why kill a perfectly working kdict ( #170730 ) before we have a working replacement is beyond me. (relax, this is just a rhetorical question) ;) 
Comment 3 Dario Andres 2008-12-12 19:44:23 UTC
I can confirm here using:
Qt: 4.4.3
KDE: 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2))
kdelibs svn rev. 895869 / kdebase svn rev. 895869
on ArchLinux x86_64
Comment 4 Beat Wolf 2008-12-23 11:31:50 UTC
I can also confirm, and it somehow looks like a qt bug when looking at the code.
Comment 5 Aaron J. Seigo 2008-12-23 18:27:00 UTC
yes, this is an upstream Qt bug.

and why do people have to offer random opinions on things they have absolutely no clue about? (don't worry, that question is also rhetorical)
Comment 6 Beat Wolf 2008-12-23 18:35:46 UTC
Well, i said that i looked at the code, and by reading the code the only conclusion i could make was that it's a qt bug, because there seemed nothing wrong with the applet code. So i was thinking that this info might help someone