maemo.org - Talk - [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

is there a way to make the space surrounding a picture in the widget transparent ? i have a widget 87 X 83 and the icon is a football 50 X 50 with white background, can i change that background to transparent ? the provided choices are different colors.
thanks

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by AgogData (Post 894536)

Set 1 to Yes

http://wiki.maemo.org/images/thumb/5...px-Snap031.png

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Could it be possible for the QBW to be used to record a Macro of onscreen keystrokes?

I have been wondering if a record button can be implimented to run as "Always on Top", so that if when using MicroB or possibly the calculator you could tap on the play button and it will repeat the gestures?

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by MINKIN2 (Post 899683)

AFAIK, due to the nature of HD/HH no such behaviour for an HH-applet can be implemented ... and can't think of any other current Maemo 5 app which such UI capabilities

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Thanks No!No!No!Yes!

I have been looking in to other mouse recording software too, things are looking very slim.

Cheers anyways mate

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Ehi NoNoNoYes .. :)
I have a small problem...
I've the message of "image not found" if i put an image in /home/user/.queen_beecon_dir ... :/
No prob if i put the image in MyDocs/.images/.queen_beecon_dir ...
Have i become a noob or what ? T_T
I've tried even removing/purging the app or rebooting... but nothing -.-

Heeelp bro T_T

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by Dany-69 (Post 901404)

Uhm ... permissions?
What QBW version?
Please post export and, if possible, v4 log of offending QBW.
Ciao.

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Qbw 1.3.2 ..
And it happen with every beecon i create/import ... old widget import instances that worked perfectly now give image not found...

For example this:

http://www.maemomeego.net/viewtopic.php?f=64&t=1384

PS: yon mean the permissions of the directory /home/user/.queen_beecon_dir ?
mmm ... i don't know xD .. how can i see it ?

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by Dany-69 (Post 901404)

Hi
You have mistake in the name of the images folder...
you need put you images in the:

Code:

/home/user/MyDocs/.images/queen_beecon_dir

instead the:

Code:

/home/user/MyDocs/.images/.queen_beecon_dir

you put the dot in the name of image directory....

the /home/user/.queen_beecon_dir is for the LOG files...

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Schtur ... you're wrong xD

That directory isn't only for log files... I have already used that for the images... and the same wiki say that it is possibile.,..

Besides you need the point dear :)

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by Dany-69 (Post 901436)

Yeah, /home/user/.queen_beecon_dir and contained files
check which user you copied them with

ssh into n900 and check perms and owners with ls -al

Directories checked for images are in this order:
1) /home/user/MyDocs/.images/queen_beecon_dir/
2) /home/user/.queen_beecon_dir
3) /usr/share/icons/hicolor/48x48/hildon/

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by No!No!No!Yes! (Post 901656)

/home/user/.queen_beecon_dir permissions :

drwxr-xr-x 2 user users 4096 Dec 21 17:51 .queen_beecon_dir

Something wrong?

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Is there a way to save all your beecons and automatically restore them? I use about 60 beecons and disastrously (has happened twice) my beecons did not load up on booting up the device. They had all magically transformed into the default app ok beecon. Adding all these beecons back (having to import file into beecon/buffer) takes ages. Would be great if I could just load all of them at once.

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by etuoyo (Post 902414)

uhm... i never tested with these many beecons ... but quicker way to be safe is to regularly backup your configuration file ~/.queen_beecon so if your kind of reset condition happens you just restore the file and issue a killall hildon-home to go back.
I still havent studied a way to automatically istantiate multiple QBW from for example a script
If I have some spare time in this holidays I'll give it a shot

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

@D69: Paisa' ... are you still in the mud? Please post v4 log, directory permissions look ok do images look the same?

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by No!No!No!Yes! (Post 902668)

Thanks. What is the full path to the folder with the configuration file? I found /home/user/.queen_beecon_dir/ but that just contains a log file which seems blank.

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by No!No!No!Yes! (Post 902668)

Hi No!No!No!Yes!
I have this problem too... I have 17 widgets...
I do backup to this file ( /home/user/.queen_beecon) and if I restoring this file, all my QBW is gone... And after this action I can't add any QBW... I need reset this file to default, like you wrote in wiki:

Code:

sudo gainroot (only if you are not already root)

rm /home/user/.queen_beecon

killall hildon-home

After this I need do action like you wrote here for restoring of all my widgets: Import Procedure

Would be great if we could just load all of them at once.

Thanks

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by Schturman (Post 902705)

Code:

sudo gainroot (only if you are not already root)

rm /home/user/.queen_beecon

killall hildon-home

After this I need do action like you wrote here for restoring of all my widgets: Import Procedure

Would be great if we could just load all of them at once.

Thanks

Please describe your problem in more detail and especially the backup/restore steps...
When you need to restore the file? After a reflash?

I never tried this but I think that if you
1) save .queen_beecon
2) reflash
3) install QBW package
4) restore .queen_beecon
5) keep adding widgets with "gear icon" "desktop menu" "Add widget" "Queen BeeCon Widget"

They will be restored ok.

Warning! There is a known glitch in this procedure ...
Suppose you create beecon 1 2 3 4 5 6 7 8 9 10 (This are IDs given directly by HildonHome)
Then you delete beecon 4 5 6
Then you backup, reflash, restore .queen_beecon
When you add QBW widgets again as per previous procedure in step 5), instances 1 2 3 should restore ok ... then HH generates instance IDs for 4 5 6 which are not any more in conf file, so they get reset and recreated from scratch (with default appearance), then you go on with 7 8 9 10 which should restore ok.
Just delete 4 5 6 by hand

As I said I was not able to find (but I confess I didn't look very deeply into it) a way to interact with Hildon-Home/Desktop (gconf, dbus ...) in order to automatically:
1) add new QBWs (and this could also be useful to create .deb packages already crafted with preconfigured beecons)
2) restore,sanitize,normalize the instance ids sequence both in conf file and in HH system files.

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by No!No!No!Yes! (Post 902778)

I'll explain what I do...
1) for backup I copied the file ".queen_beecon" to the MyDocs.
2) I tried edit one of my widgets and by mistake I deleted the CMD in "Edit CMD" option.
3) I copied back the file ".queen_beecon" from MyDocs to /home/user
4) I go back to desktop and all my widgets is gone (not only QBW)
5) I tried add QBW again to the desktop, but it can't done.
6) I reset the file ".queen_beecon" to default one.
7) I added again all widgets one by one with "Import procedure" (I have backup from Export procedure)

I thought copying a file ".queen_beecon" that's enough + adding the widget from desktop... But it's not... :)

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Okay found the .queen_beecon file. It is the one in /home/user right?

So if I copy it to PC or something and my beecons suddenly disappear again I just copy this file back to this folder and all my beecons will be restored or I need to enter a code in terminal?

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

hi all !!!
i have read some of the pages of this thread but could not understand anything i have had this widget a few month ago, and could not find how to use it!(i didn't search too) of course i am a noob .so is this only for advanced user ?or there is any tutorial page or thread for us? should i try this one more time?could i brick my n900 if i misuse or do something which i do not understand?

DBUS Event Monitoring - triggering power button - need help creating match rule

I would like to execute a widget by pressing the power button. But my tests didn't succeed.

I'm able to trigger the power button with dbuscron or dbus-scripts.

dbuscron example:
(bus, message_type, source, interface, object_path, member, destination, arguments, command)
S signal * org.freedesktop.Hal.Device /org/freedesktop/Hal/devices/computer_logicaldev_input Condition * ButtonPressed;power /execute/some/script.sh

dbus-scripts example taken from powerlock:
/execute/some/script.sh * /org/freedesktop/Hal/devices/computer_logicaldev_input null org.freedesktop.Hal.Device Condition ButtonPressed power

For my (obviously wrong) understanding the match rule in QBW should look something like:
type='signal',interface='org.freedesktop.HAL.Devic e',member='Condition',path='/org/freedesktop/HAL/devices/computer_logicaldev_input',arg0='ButtonPressed',ar g1='power'

Unfortunately all my tests failed. I tested with different variations (entering/leaving wildcards, playing around with member and arguments, etc.), but didn't succeed.

I need a hint, how to adjust the match rule...

Re: DBUS Event Monitoring - triggering power button - need help creating match rule

Quote:

Originally Posted by Psioneer (Post 904011)

I would like to execute a widget by pressing the power button. But my tests didn't succeed.

I've found the solution:
The above mentioned match rule works like it should. But there seems to be a QBW problem with updating the widgets after editing the match rule:
Everytime I edit the match rule, the widget doesn't react on DBUS events anymore. I have to delete the widget an recreate it again. The new widget is the same as the deleted widget - with the edited match rule.

After this delete/recreate procedure the widget works without problems.

This concerns only editing the match rule - every other setting can be changed without breaking the DBUS event listening.

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by etuoyo (Post 903474)

Problems with hildon-home widget is that all non-standard (custom made) ones get disabled by the system in case an error occurs in one of them. Only plugins listed in this file get loaded again /etc/hildon-desktop/home.safe-set

If it happens as you described, you can just keep adding beecons back again with step 5 in this post http://talk.maemo.org/showthread.php...ostcount902778

Re: DBUS Event Monitoring - triggering power button - need help creating match rule

Quote:

Originally Posted by Psioneer (Post 904063)

Possibly a bug ... I'll look into it soon.
As workaround just try:
1) to edit rule
2) set DBUS monitor to off
3) save
4) re-open settings
5) set DBUS monitor to on
6) save again

See if this work, please.

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by nicholes (Post 903490)

As a start, have a look at examples part of the wiki http://wiki.maemo.org/Queen_BeeCon_Widget#Beecons

See if it helps!

Re: DBUS Event Monitoring - triggering power button - need help creating match rule

Quote:

Originally Posted by No!No!No!Yes! (Post 904947)

See if this work, please.

Hi No!No!No!Yes!

In hope to find a solution on my own, I tested that already before. Unfortunately that doesn't work.
Furthermore: Just disabling/enabling the DBUS monitoring (without editing the rule) also breaks the monitoring.

So it seems that any change of the section "DBUS Event Monitoring" leads to this behaviour.

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Thanks, Arno.
Effort appreciated indeed!
:D

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by No!No!No!Yes! (Post 893936)

OK ... Queen BeeCon Widget release 1.3.2 is now in extras-testing queue and candidate to reach EXTRAs
Partial Change Log

Code:

queen-beecon (1.3.2)



 * New: -    

 * Changed: Enabling logger verbosity in Logger Verbosity Button in Advanced Settings and Tools Dialog Box enables logging if not enabled on startup by touchlogfile      

 * Changed: Logger timestamps are now printed in ISO 8601 encoded string, relative to the Coordinated Universal Time (UTC) 

 * Bugfixing: Version was not displaying in About Box because of font too big; fixed



queen-beecon (1.3.1)



 * New: -    

 * Changed: -

 * Bugfixing: Incorrect error "error enabling QBW_SUBSYSTEM_TIMER" report in TIMER subsystem rearm



queen-beecon (1.3)



 * New: Ability to sense Phone Orientation and execute scripts accordingly + Relevant configuration parameters (updOnOrientation)

 * New: Phone Orientation Parameter Variables substitution for using with scripts which hold $QBW_ORIENTATION_MODE, $QBW_ORIENTATION_STAND, $QBW_ORIENTATION_FACE, $QBW_ORIENTATION_X, $QBW_ORIENTATION_Y, $QBW_ORIENTATION_Z

 * New: Ability to sense GPS/Location information and execute scripts accordingly + Relevant configuration parameters (GPSsettings)

 * New: GPS/Location Parameter Variables substitution for using with scripts which hold $QBW_LOCATION_FIX current position FIX in string form

 * New: Added option to wrap text results and relevant configuration parameter resWrapLongLines 

 * New: New about box in Advanced Settings dialog Box with Application Name, Description, Version, Buttons for "Visit website" "Report bug" "Donate", Copyright info 

 * New: Added confirmation in Command Deletion Dialog Box

 * New: Added the possibility to completely hide widget and display only the animation when updating (useful for example to draw on-click/press FX frames and visual feedback to buttons)

 * New: Parameter Variables substitution for using with scripts which holds the current X position of QBW widget ($QBW_POSITION_X); useful for dynamic update/processing of widget according to its position on screen  

 * New: Parameter Variables substitution for using with scripts which holds the current Y position of QBW widget ($QBW_POSITION_Y); useful for dynamic update/processing of widget according to its position on screen  

 * New: Implementation of toggle for multi-click support (quicker click response if disabled); with relevant settings & configuration parameter "multiClick"   

 * New: Implementation of DBUS methods: reset_rearm_connection

 * New: Implementation of DBUS methods: reset_rearm_location

 * New: Implementation of DBUS methods: reset_rearm_orientation

 * New: Implementation of DBUS methods: reset_rearm_dbus_monitor

 * Changed: Complete QBW icons restyle!!!

 * Changed: Changed some settings sensitivity logic according to enablement of relevant function

 * Changed: Command Input Buffer in Advanced Settings Dialog Box now accepts linebreaks in the input for improved command readability

 * Changed: Progress Animation is now not shown if widget is set to invisible 

 * Changed: @connection events now have their management subsystem and gets activated only for instances requiring it 

 * Changed: Changed logger verbosity @connection event 

 * Changed: Restyle in Update Policy Settings 

 * Changed: UI Restyle in Advanced Settings and Tools Dialog Box  

 * Changed: UI Restyle in Widget Size Settings  

 * Changed: UI Restyle in Widget Positioning Settings  

 * Changed: More verbosity for Pango Markup Language inconsistencies notification (Now instance id and offending command title are displayed) 

 * Changed: Optimization in wakeup/sleep logic (better error management and notifications)

 * Bugfixing: Instance parameters related to commands (instanceTitle, instanceCmd) where not poperly updated when edited both in Advanced Dialog Box and in Command Add/Edit/Delete dialog box; fixed

 * Bugfixing: Network connection/disconnection logic; fixed

 * Bugfixing: In Advanced Dialg Box, export of command not in list caused SEGFAULT; fixed



queen-beecon (1.2)



  * New: Release Candidate to Extras (1.0.53 -> 1.2)    

  * Changed: Release Candidate to Extras (1.0.53 -> 1.2)

  * Bugfixing: Release Candidate to Extras (1.0.53 -> 1.2)



queen-beecon (1.0.53)



  * New: Parameter Variables substitution for using with scripts which holds the current width of QBW widget ($QBW_WIDTH); useful for dynamic recalculation of click hotspots 

  * New: Parameter Variables substitution for using with scripts which holds the current height of QBW widget ($QBW_HEIGHT); useful for dynamic recalculation of click hotspots

  * New: Parameter Variables substitution for using with scripts which holds the exit status of the last previous executed command ($QBW_PREVIOUS_EXIT_STATUS)

  * New: Added new Network Connection Event condition (NETWORK__PASSTHROUGH) which will trigger the execution of command at every Network Related event. Management of the connection event status will be completely delegated to the command through $QBW_IS_CONNECTED and $QBW_EXEC_REASON=="QBW_CONNECTION_EVENT" Parameter Variables substitution.  

  * Changed: Optimized "cancel on exec in progress" logic   

  * Bugfixing: Some network connection status change issues; fixed



queen-beecon (1.0.52)



  * New: In Command and Instance import in Advanced Settings and Tools Dialog Box, command title is now checked for existence, if existent "+"s are appendend till name is unique  

  * New: In Add/Edit Command Dialog box, command title is now checked for existence, if existent, user is now asked for unique name  

  * Changed: -   

  * Bugfixing: Both in Settings and in Advanced Settings and Tools Dialog Box, Command Selection button was not correctly re-populated after operations on commands list (add/delete/import); fixed



queen-beecon (1.0.51)



  * New: Added Reset/Truncate Logfile action to Logger Verbosity Button in Advanced Settings and Tools Dialog Box

  * Changed: -   

  * Bugfixing: -



queen-beecon (1.0.5)



  * New: Possibility to directly modify the "rememberMe" parameter from the output of the executed command (without using the DBUS interface which is much slower) for using with scripts which need to hold/manipulate status or persistency information. Just echo the following string (which will not be displayed) as output of your command "QBW_REMEMBER_ME(<content to be remembered>)" no angle brackets; escape "close round bracket" like this "\)" to store it as ")" 

  * Changed: Extended warning message in case of inconsistent Pango Markup Language output ("QBW Warning! Possible Pango Markup Language inconsistent/unterminated Tag!")   

  * Changed: Extended warning message in case of inconsistent/non-UTF-8 output in TestDrive output Buffer ("QBW Warning! Expected/Shown Command Output mismatch. Possible charset different from UTF-8!")   

  * Bugfixing: QBW re-enable on double-click logic bugged; fixed



queen-beecon (1.0.4)



  * New: Implemented the possibility to have the Progress Animation displayed at widget click X,Y coordinates; with relevant configuration parameter "progressAnimationAtClickXY"   

  * New: Implemented the possibility to hide the background Canvas on click both for Beecons and Snippets with relevant configuration parameter "hideClickCanvas"   

  * Changed: Some optimizations in QBW at startup, expecially for instances with execute @startup flag; should speed up widget appearance

  * Changed: Checks for obsolete instances in configuration file moved to Advanced Settings and Tools Dialog; check is performed upon entering. 

  * Changed: Some optimizations in progress icon animation logic

  * Changed: Some optimization in multiple-clicks management

  * Bugfixing: Command output for Test Drive in Advanced Settings and Tools Dialog still buggy and not displaying complete output; fixed

  * Bugfixing: Logic for multiple clicks count was a bit bugged; fixed

  * Bugfixing: DBUS Signal emission at end of command execution was misplaced ; fixed

  * Bugfixing: Logging info incorrect for timeout seconds count function GetSeconds; fixed



queen-beecon (1.0.3)



  * New: Added button to change Logger Verbosity in Advanced Settings and Tools Dialog Box

  * New: Implementation of Command and Results image orientation angle (w/ relevant configuration parameters)

  * New: Added edit box in Settings Dialog for "rememberMe" value. Can now be initialized also from widget and not only via DBUS method  

  * New: Parameter Variables substitution for using with scripts which holds the number of times a QBW was pressed/clicked: $QBW_CLICKS_COUNT; useful for handling single/double/triple... clicks and behave accordingly (Tested up to 12 ... :) )

  * New: Parameter Variables substitution for using with scripts which hold X and Y coordinates where a QBW was pressed/clicked: $QBW_CLICK_X, $QBW_CLICK_Y; useful for handling different arbitrary/dynamic hotspots on widgets via launched shell scripts 

  * Changed: Now QBW instances with status disabled/minimized (black small 60x60 inactive sleeping bee icon) are enable again on double-click and non on single-click

  * Bugfixing: TestDrive in Advanced Settings and Tools Dialog Box was not fetching the whole command output; fixed   

  * Bugfixing: Typos in "Edit Cmd" Dialog Box title; fixed   

  * Bugfixing: Not proper memory deallocation of some strings parameter in Settings Dialog; fixed    



queen-beecon (1.0.2)



  * Source Modules: Changed architecture of source module ... now split into single modules according to QBW subfunctions ... expect some sneaky regressions!!!

  * New: Parameter Variables substitution for using with scripts which holds Network Connection status: $QBW_IS_CONNECTED (true=QBW Instance is connected to the network (either WLAN or GPRS) false=QBW Instance is NOT connected to the network (either WLAN or GPRS))

  * Changed: In Settings Dialog Box changed "Custom(")" to "Custom(Secs)" for custom timer label

  * Changed: In Advanced Settings and Tools Dialog Box it's now possible to scroll dialog both vertically and horizontally. So all buttons will be accessible even if you have big fonts 

  * Changed: In Advanced Settings and Tools Dialog Box added more checks for Import Instance/Command Data (It should now be more restrictive on Import Data consistency/congruency)

  * Bugfixing: System Proxy fetching logic bugged; fixed

  * Bugfixing: reset_rearm_timer DBUS method call was not disabling timer when timer update was disabled; fixed

  * Bugfixing: set_param_uint32 DBUS method call had problems if values = 0; fixed



queen-beecon (1.0.0.1)



  * New: Nothing - Release Candidate to Extras (0.1.9.9 -> 1.0.0.1)    

  * Changed: Nothing - Release Candidate to Extras (0.1.9.9 -> 1.0.0.1)

  * Bugfixing: Nothing - Release Candidate to Extras (0.1.9.9 -> 1.0.0.1)



queen-beecon (0.1.9.9)



  * New: Added "On Sight" Update Policy (If flagged, content is not updated if widget is out of sight (on other desktop) or if display is locked or in stand-by)   

  * New: Parameter Variables substitution for using with scripts which holds "On Sight" or "Out Of Sight" status: $QBW_ON_SIGHT (true=QBW Instance is "ON SIGHT", that is widget is on current desktop and display is not locked or on stand by. false=QBW Instance is not on current desktop and visible or display is off or on stand by)

  * New: DBUS method "is_on_sight" which returns true (QBW Instance is "ON SIGHT", that is, widget is on current desktop and display is not locked or on stand by) or false (QBW Instance is not on current desktop and visible or display is off or on stand by)

  * Changed: Optimized usability of settings for Widget Width and Height

  * Changed: Optimized progress animation logic for visibility when instance not On Sight

  * Bugfixing: -

See complete Change Log in the WIKI

Time for v1.3.2 to go to Extras-Testing
Please go to this link, test and thumb-up QBW so that it can be promoted and reach EXTRAs ASAP

... thanks to you all Supporters and Testers ... QBW v1.3.2 promoted to EXTRAS!

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

hi,

some of my scripts dont work anymore with the latest
qbw version, for instance a command like

if [ $QBW_CLICKS_COUNT -ge 2 ]; then conboy ;fi

a double click is not recognized anymore. changing
the condition to -ge 1 works?!

Blues

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by BluesLee (Post 909218)

http://wiki.maemo.org/Queen_BeeCon_Widget#Update_Policy

http://wiki.maemo.org/images/thumb/f...px-Snap034.png

Make sure 5 is set to "yes"

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

hi, I've been playing with your program which is very nice,but I'm new with using linux and I have a quick question I made a snippet to run on my desktop to show the cpu speed and this is the command the I use..

echo CPU @ `awk '{print $1/1000" MHz"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq`

is this correct,it shows on my desktop but I'm confused on which button to set so it shows automatically when it on 250,500 or 600, without having to click on the snippet. Thank you

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Hi, sorry if this has been covered, I can't find much through google so I thought I'd ask.

How do I string a few terminal commands together, so if for example, I was creating a widget to put my wireless card into monitor mode and I wanted to run the following

Code:

sudo gainroot

ifconfig wlan0 down

iwconfig wlan0 mode Monitor

ifconfig up

How would I do so?
I can get a single command to work, but how do I string it together.

Thanks

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by SavageBrat (Post 909242)

You need a system event to be real-time notified about CPU frequency changes but I can't think of any right now which signals changes in this area. (DBUS, other ...)
However you can use timer or desktop switch policies to have a very rough update.
Ciao.

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by James_Littler (Post 909251)

Code:

sudo gainroot

ifconfig wlan0 down

iwconfig wlan0 mode Monitor

ifconfig up

How would I do so?
I can get a single command to work, but how do I string it together.

Thanks

Like this?
http://talk.maemo.org/showpost.php?p...7&postcount=11

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Currently I have this as my command

Code:

#!/bin/sh



# gain superuser rights.



if [ `id -u` != 0 ] ; then

    exec sudo gainroot <<EOF

exec sh $0 $*

EOF

        exit $?

fi   



# put your code below



ifconfig wlan0 down;

iwconfig wlan0 mode Monitor;

ifconfig wlan0 up;



exit;

I have it set to update at click but it's not doing anything.
When I check iwconfig it says I'm still in managed mode.

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

I've still not managed to get this to work. Ideas anyone?

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

Quote:

Originally Posted by James_Littler (Post 909373)

Currently I have this as my command

Code:

#!/bin/sh



# gain superuser rights.



if [ `id -u` != 0 ] ; then

    exec sudo gainroot <<EOF

exec sh $0 $*

EOF

        exit $?

fi   



# put your code below



ifconfig wlan0 down;

iwconfig wlan0 mode Monitor;

ifconfig wlan0 up;



exit;

I have it set to update at click but it's not doing anything.
When I check iwconfig it says I'm still in managed mode.

Have you tried the script from a shell prompt as user: "user" (your credentials when running script from qbw)?

Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread

terminal exits faster than I can see whats happening
iwconfig says its still in managed mode