maemo.org - Talk
Page 103 of 140 « First 93101102 103 104105113 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread (https://talk.maemo.org/showthread.php?t=45388)

etuoyo 2010-12-24 14:58
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?

nicholes 2010-12-24 15:41
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?

Psioneer 2010-12-25 12:33
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...

Psioneer 2010-12-25 15:21
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.

No!No!No!Yes! 2010-12-27 00:48
Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread
 
Quote:
Originally Posted by etuoyo (Post 903474)
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?
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

No!No!No!Yes! 2010-12-27 00:49
Re: DBUS Event Monitoring - triggering power button - need help creating match rule
 
Quote:
Originally Posted by Psioneer (Post 904063)
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.
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.

No!No!No!Yes! 2010-12-27 00:54
Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread
 
Quote:
Originally Posted by nicholes (Post 903490)
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?
As a start, have a look at examples part of the wiki http://wiki.maemo.org/Queen_BeeCon_Widget#Beecons

See if it helps!

Psioneer 2010-12-28 09:42
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.

No!No!No!Yes! 2010-12-29 07:41
Re: [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread
 
Thanks, Arno.
Effort appreciated indeed!
:D

No!No!No!Yes! 2010-12-30 00:00
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!


All times are GMT. The time now is 17:01.
Page 103 of 140 « First 93101102 103 104105113 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8