Notices

Originally Posted by Example from QBW Greedy Desktop Switcher

command for retrieving the horizontal position where a horizontal bar widget is clicked:

PHP Code:

dsk=1;
if [ "_$QBW_EXEC_REASON" == "_QBW_CLICK" ]; then
   gconftool-2 -s /apps/osso/hildon-desktop/views/current -t int `expr $QBW_CLICK_X / 89 + 1`;
fi;
exit `expr $dsk + 2` 


Originally Posted by Vintrc

Hi,
anyone knows about some command for hide and show all desktop?
I mean one button will be everytime on desktop and when i press it, each icons, widget etc. hide and next show back.. because if i have some nice wallpaper, it would be fine

Originally Posted by No!No!No!Yes!

@slarti: Very interesting use case here
I don't know the ZWAVE controller - as a premise - but:

Is there any way for the ZWAVE to report an unsolicited status of all/some sensors, like for example if you have a temperature sensor attached to it, is it possible to be notified by ZWAVE about a change in the temperature or you have to periodically issue a polling wget?

Apart from wget command, is there any other way to change the status of devices (ex. some impulse on the device itself, switch, potentiometer...)?

Issue here, for representing devices status, is to be as much real-time as possible, thus triggering a beecon status update every time it is necessary (and avoid timered polling on all devices to know their status - what timer period? how much battery will this consume?)

How can the ZW initiate a communication with the N900, if possible?

Originally Posted by No!No!No!Yes!

The DIM part is not as much difficult as it seems on first sight.
In QBW you can sense the tap/click position on a widget and return a different exit status value which will be converted into an image; precision and tolerance is indeed up to you ... you want to manage 30 different intermediate levels you just create 30 different images and alter some divider in the script


I'll follow up on this as soon as I receive some of your feedback on the matter

Bye.

Originally Posted by matristain

Hi , Just starting with QBW I`ll appreciate some help.

I have this code on a call.sh i create a desktop icon to run it.
It does its work but i am looking for a better way to do this:

Call XXXXXXXXXX number , if call is till a active after 275 seconds Hang Up the call and call XXXXXXXXXX again.

PHP Code:

#!/bin/sh

dbus-send --system --type=method_call --print-reply --dest=com.nokia.csd.Call /com/nokia/csd/call com.nokia.csd.Call.CreateWith string:"XXXXXXXXXX" uint32:0

sleep 275

output=`dbus-send --system --dest=com.nokia.csd.Call --print-reply=literal /com/nokia/csd/call/1 com.nokia.csd.Call.Instance.GetStatus`
if [ "$output" == "   uint32 8" ]; then
    dbus-send --system --dest=com.nokia.csd.Call --print-reply /com/nokia/csd/call com.nokia.csd.Call.Release
    sleep 4
    sh /home/user/.call/call.sh
    exit
    
else
    exit
fi 


What i want is to stop the loop at any time becouse when I hang up manualy the call this scripts continue running and It will hung up any other call i make withing the 275 seconds.

NOTE: this is for a toll free number for less than 5 minuts call, and its very useful using Hands Free car kit.

Sorry for my english, still trying to improve it.

Originally Posted by matristain

Can QBW handle the "Long press" to avoid axidental execution?

Originally Posted by No!No!No!Yes!

As quick suggestions ...
Avoid sleep 275
And in very-very-very-very metacode:
On widget startup (phone on ecc) $QBW_EXEC_REASON=="QBW_STARTUP_UPDATE", explicitly reset beecon timer parameters (delayIndex = 0 customIntervalSecs = 275) via DBUS method call set_param_uint32 see syntax in the wiki; after resetting both parms, issue a reset_rearm_timer method to the widget

On widget click $QBW_EXEC_REASON=="QBW_CLICK" , check if your very specific call active via usual dbus enquiries
If your specific call is not active (didn't dig how to check this) initiate call and explicitly set beecon timer parameters (delayIndex = 9 customIntervalSecs = 275) via DBUS method call set_param_uint32 see syntax in the wiki; after setting both parms, issue a reset_rearm_timer method to the widget
If your specific call is active (didn't dig how to check this) terminate call and reset widget timer as per QBW_STARTUP_UPDATE step

If execution of script is due to $QBW_EXEC_REASON=="QBW_TIMER_UPDATE" , check if specific call active via usual dbus enquiries
If your very specific call is active, drop call, and reinitiate call (275secs timer will still be in place)
If your very specific call is not active, reset timer as per previous steps

Issue specific exit status at the end of every condition if you want to draw different icons according to call status statuses

Hope this helps