Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 90521 - xfce-4.2.0 launch panel buttons - one-shot only
Summary: xfce-4.2.0 launch panel buttons - one-shot only
Status: VERIFIED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: XFCE Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-26 11:47 UTC by genbug
Modified: 2006-02-17 15:53 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description genbug 2005-04-26 11:47:27 UTC
If I click on a button on the panel it loses its border , greys then comes back to the ungreyed icon but still without the border.

This refelects a bug in the state of the button because it will no longer register a mouse click.

It is necc to leave the button area and re-enter to use it again.
This was not the case in 4.0.6



Reproducible: Always
Steps to Reproduce:
1.Click the terminal button , a window opens and the button comes back up.
2.Click again to open a second terminal , no state change , nothing happens.
3.Move out then come back and click and it works.



Expected Results:  
Multiple clicks should open multiple windows. The button should return to its 
normal active state with a border.
Comment 1 Brad Cowan (RETIRED) gentoo-dev 2005-07-21 20:18:38 UTC
this was by design, there is a short delay so you don't accidentally open
multiple instances by accident
Comment 2 genbug 2005-07-27 03:57:28 UTC
please re-read the bug I submitted.

It is not a case of delay , there is a bug in the state of the button that stops
it funtionning correctly.
Comment 3 Brad Cowan (RETIRED) gentoo-dev 2005-08-14 14:28:29 UTC
have you tried 4.2.2?
Comment 4 Brad Cowan (RETIRED) gentoo-dev 2006-02-17 13:02:30 UTC
please reopen if this still is a problem in 4.2.3
Comment 5 genbug 2006-02-17 15:53:28 UTC
confirmed.

this has now been fixed.

Thx.