| Summary: | Kill Process can't be clicked | ||
|---|---|---|---|
| Product: | [Unmaintained] ksysguard | Reporter: | Martin Koller <kollix> |
| Component: | Process Controller - krunner part | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | arno, johnflux, vit.gorbunov |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Updated for 64bit | ||
|
Description
Martin Koller
2010-01-09 14:07:26 UTC
Just to confirm, you are pressing ctrl+esc and not doing anything else and the kill button is not drawn as disabled? When you first bring up the dialog no processes are selected so the button should be disabled and so grayed out. On Saturday 09 January 2010 16:40:15 John Tapsell wrote: > --- Comment #1 from John Tapsell <johnflux gmail com> 2010-01-09 16:40:11 --- > Just to confirm, you are pressing ctrl+esc and not doing anything else and the > kill button is not drawn as disabled? Of course I selected a process before I tried to kill it ... > When you first bring up the dialog no processes are selected so the button > should be disabled and so grayed out. I know the difference between a disabled and an enabled button (I'm a Qt programmer). This bug is about the enabled button. (In reply to comment #2) > I know the difference between a disabled and an enabled button (I'm a Qt > programmer). > This bug is about the enabled button. I know - I was trying to work out if it was a disabled button that is being drawn as enabled, or an enabled button behaving as if it's disabled. I can't reproduce myself, but two other people can. *** Bug 222024 has been marked as a duplicate of this bug. *** I can confirm this, using trunk (r1067626). The button behaves normally after I move the mouse over the search field or the combobox. As soon as other widgets do the "highlight" effect, the pushbutton seems to work ok again. But if I just fire up ksysguard, click on a process and hover the button, it behaves as described above. On Sunday 10 January 2010 13:57:02 Arno Rehn wrote:
>
> The button behaves normally after I
> move the mouse over the search field or the combobox. As soon as other widgets
> do the "highlight" effect, the pushbutton seems to work ok again.
Not in my case. The button does never work.
As it was noted on the mailing list, it's actually only a small part of the button which reacts to mouse events (regardless of the widgets that were highlighted before). The reactive part of the button seems to be on the right side. Just for reference: http://lists.kde.org/?l=kde-core-devel&m=126315608221251&w=2 Created attachment 39796 [details]
Updated for 64bit
This copies some of the code from pinotree's patch to add 64bit support.
I'm an idiot. Ignore last patch. Aseigo fixed - thanks. |