Allow a user to set any timeout for the buttons

Bug #262603 reported by Ketil Wendelbo Aanensen
4
Affects Status Importance Assigned to Milestone
Universal Applets
Confirmed
Medium
Universal Applets Core

Bug Description

The timeout is still too fast for my clumsy fingers on a touchpad. I think I need 2-3 seconds. I'd like to set the timeout globally, and I'd like to be able to have buttons displayed all the time if I so choose.
Also I'd like to see the buttons have a click effect, so I can see if my click is picked up, or if there's something wrong.

Revision history for this message
Natan Yellin (aantny) wrote :

Instead of adding an option for the fade-time, I'd like to just give the timeout a saner settings by default. We'll still add a "always show buttons option" to disable the fading altogether.

Changed in universal-applets:
assignee: nobody → universal-applets-core
importance: Undecided → Medium
milestone: none → 0.1-first-release
status: New → Confirmed
Revision history for this message
Compizuser01 (meneerjansen00) wrote :

I can confirm this. When I try to click the buttons they fade out before I can click them.

Revision history for this message
Natan Yellin (aantny) wrote :

I'm pretty happy with way the timeout works as of revision 512.

@Compizuser01, Ketil:
Please test and let me know what you think.

Revision history for this message
Compizuser01 (meneerjansen00) wrote :

At present I can't even move the screenlets and no buttons appear (revision 518). But when they did appear in the last version I still could not click on the buttons. Nothing happened.

Revision history for this message
Natan Yellin (aantny) wrote :

@Compizuser:
Can you paste the output of running the following command and then adding screenlets:
melange --replace -oSTDOUT -l5

Note: The above command will also close all currently running screenlets.

Revision history for this message
Compizuser01 (meneerjansen00) wrote :

I use rev. 526 now. Still no buttons on the screenlets. Still much trouble to get them to auto start: they keep on disappearing in the autostart tab of the Manager if i start one manually.

Commandline output:
[code]
$ melange --replace -oSTDOUT -l5
2008-10-02 12:38:21,067 - DEBUG - Melange: Logging initialized
2008-10-02 12:38:21,068 - INFO - Checking for another running instance...
2008-10-02 12:38:21,075 - INFO - No other instances found.
2008-10-02 12:38:21,142 - DEBUG - Melange: Done.
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/screenlets/melange.py", line 690, in realize
    self.create_menu()
  File "/usr/lib/python2.5/site-packages/screenlets/melange.py", line 265, in create_menu
    self.builder = gtk.Builder()
AttributeError: 'module' object has no attribute 'Builder'
2008-10-02 12:40:08,787 - DEBUG - Melange: Recieved message shape-changed: Shutdown1: 0
2008-10-02 12:40:08,804 - DEBUG - Updating input shape
2008-10-02 12:40:09,015 - DEBUG - expose event
2008-10-02 12:40:09,039 - DEBUG - Melange: Recieved message shape-changed: Shutdown1: 0
2008-10-02 12:40:09,053 - DEBUG - Updating input shape
[/code]

Success w/ developing. :)

Revision history for this message
Natan Yellin (aantny) wrote :

Compizuser, can you still confirm this?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.