Re: [feedback request]shortcutd
 

@Lacedaemon, unluckily, proximity sensor is binary and we cannot control the distance it operates. So we are stuck with those accidental triggers.

Re: [feedback request]shortcutd
 

Hiya,

one request - can you please make Shortcutd control the action of the Power button? There's a program called tweakr that can control it (to a certain degree)... it would be cool if this was added to Shortcutd....

Cheers

Re: [feedback request]shortcutd
 

i didnt read the thread but wouldnt be surprised if this is a common complaint:

i would like to have the app be configurable so i can use the shortcut on the camkey button only, the proximity sensor is constantly getting accidentally triggered and theres no way to disable it

Re: [feedback request]shortcutd
 

It appears that you also didn't bother to read the application description before you installed it.

Re: [feedback request]shortcutd
 

@jerryfreak, the application is fully configurable in the settings.

Re: [feedback request]shortcutd
 

Shortcutd 0.1.1-2 is now in extras-testing, the main changes are the configuration options allowing better personalization.
Please help us to test it :)

Re: [feedback request]shortcutd
 

The extra configuration options are welcome and very nice. I just noticed that my battery is almost dead really fast and looked what might be causing it and shortcutd was using 99.4% cpu continually! I rebooted and it seems fine now.

Re: [feedback request]shortcutd
 

What were the (exact) shortcutd settings you were using when this happened?

Re: [feedback request]shortcutd
 

I cannot go and look right now since I'm afraid I'll be all out of battery (don't have the charger with me right now). But I have both enabled, dashboard for camkey short, phone for camkey long, back for proximity short, and menu for proximity long.

The change I made with this version were disabling vibration and the enabling shortcut by a really long proximity. These were the new configuration options I was referring to.

Re: [feedback request]shortcutd
 

I tried producing all possible input/event combinations with those settings for several times but I was unable to reproduce the problem. Could have been some weird issue with HAL/dbus. Will keep an eye on that.