The Following User Says Thank You to Wonko For This Useful Post: | ||
|
2011-01-16
, 15:35
|
Posts: 561 |
Thanked: 75 times |
Joined on Jan 2010
@ Spain
|
#302
|
Well, this strongly depends on the clock style.
I think the only clock style that currently uses that field follows the python datetime strftime() formatting as described in: http://docs.python.org/library/datet...ptime-behavior
E.g., something like "%H:%M" should display the clock as "Hour:Minute".
This clock style was posted here some time ago.
|
2011-01-17
, 00:08
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#303
|
You're welcome.
Breaking backwards compatibility is nothing one does lightly.
In this case it appeared sensible to me.
Still, it is not the friendliest thing you can do to other developers building up on your work.
By the way, any comments on the new approach are very much appreciated.
As you notice I made the "per desktop clocks" as configurable as the "default" clock.
Currently, the settings for each "per desktop clock" are copied from the default clock when the per desktop clock is configured the first time.
I am planning to add "reset buttons" to the settings UI as well, in order to reset the per desktop clocks to the settings of the default clock.
This should make it easier to maintain consistent configurations among the per desktop clocks.
|
2011-01-18
, 02:47
|
|
Posts: 417 |
Thanked: 200 times |
Joined on Apr 2010
@ Germany
|
#304
|
|
2011-01-19
, 10:28
|
Posts: 561 |
Thanked: 75 times |
Joined on Jan 2010
@ Spain
|
#305
|
Well, this strongly depends on the clock style.
I think the only clock style that currently uses that field follows the python datetime strftime() formatting as described in: http://docs.python.org/library/datet...ptime-behavior
E.g., something like "%H:%M" should display the clock as "Hour:Minute".
This clock style was posted here some time ago.
|
2011-01-20
, 17:26
|
Posts: 1,283 |
Thanked: 370 times |
Joined on Sep 2009
@ South Florida
|
#306
|
|
2011-01-20
, 20:36
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#307
|
I noticed, that desktop scrolling gets pretty choppy when using for example desktop1 with decimal clock and desktop2 with no clock and so on.
is there any chance that could get optimized somehow?
The Following User Says Thank You to Mentalist Traceur For This Useful Post: | ||
|
2011-01-21
, 23:19
|
|
Posts: 417 |
Thanked: 200 times |
Joined on Apr 2010
@ Germany
|
#308
|
The Following User Says Thank You to NightShift79 For This Useful Post: | ||
|
2011-01-22
, 14:52
|
Posts: 482 |
Thanked: 550 times |
Joined on Oct 2010
|
#309
|
The Following User Says Thank You to skykooler For This Useful Post: | ||
|
2011-01-24
, 21:50
|
|
Posts: 417 |
Thanked: 200 times |
Joined on Apr 2010
@ Germany
|
#310
|
The Following User Says Thank You to NightShift79 For This Useful Post: | ||
Breaking backwards compatibility is nothing one does lightly.
In this case it appeared sensible to me.
Still, it is not the friendliest thing you can do to other developers building up on your work.
Which clocks in particular are causing the problems?
By the way, any comments on the new approach are very much appreciated.
As you notice I made the "per desktop clocks" as configurable as the "default" clock.
Currently, the settings for each "per desktop clock" are copied from the default clock when the per desktop clock is configured the first time.
I am planning to add "reset buttons" to the settings UI as well, in order to reset the per desktop clocks to the settings of the default clock.
This should make it easier to maintain consistent configurations among the per desktop clocks.
Advanced Clock Plugin --- Binary Clock, Desktop Version --- libswt-hildon
Stultitia Simplex --- To-Do-O --- VU Meter --- Zeecontrol
My homepage with assorted posts about my apps, Qt/QML, etc.: http://ruedigergad.com