We have a fully implemented GConf backend (originally for Maemo5), and a
half-done DConf backend.
Xizhi Zhu (Steven)
Software Engineer @ Qt
Nokia
Mobile: +358 (0)50 4801247
-Original Message-
From: qt5-feedback-bounces+xizhi.zhu=nokia@qt.nokia.com
Ok, then let's go for a QCalendar or QCalendarSystem that must be
initialised
with an enum. The constructor should default to Gregorian and there
should be
a System or Locale value to match the locale's preferred calendaring
system.
Should the default
On 24/08/2011, at 4:33 PM, Andre Somers wrote:
Personally, I think that adding this to QThread is not really needed
though. I don't see what is wrong with setting the sleep period in
milliseconds; sleep() should not be used all that much anyway.
In the same way that no-one will ever
24.08.2011, 11:25, Thiago Macieira thi...@kde.org:
On Tuesday, 23 de August de 2011 17:33:55 Konstantin Tokarev wrote:
E.g. I run the next environment on one machine: Fluxbox as WM, ROX-Filer as
file and desktop manager, GTK styled with custom gtkrc. The single way to
configure Qt
On Wednesday, 24 de August de 2011 12:59:59 Konstantin Tokarev wrote:
However I think it would be nice if somewhere was generic plugin controlled
by qtconfig
Anyone can make that. More likely, qtconfig will be a tool to configure this
plugin, as opposed to being a tool to configure Qt.
--
On Aug 23, 2011, at 3:14 PM, ext Thiago Macieira wrote:
I recommend the following order (later entries override earlier ones):
1) Qt-provided reasonable defaults
2) Qt-detected system settings, like Unix LANG; Mac and Windows windowing
system settings (i.e., the Lighthouse plugin)
Andre spaketh:
Personally, I think that adding this to QThread is not really needed
though. I don't see what is wrong with setting the sleep period in
milliseconds; sleep() should not be used all that much anyway.
Craig respondeth:
In the same way that no-one will ever need more than
On Wednesday 24 Aug 2011 07:35:33 Andre Somers wrote:
I hope you don't mind me pitching in at this point?
I am wondering what the plans are with those then. We use them heavily
in our QTimeSpan MR,
and as discussed at QtCS and remarked elsewhere before, I was even
planning to add some
of
On Wednesday, 24 de August de 2011 21:45:11 Harri Porten wrote:
Would this exception also apply to new modules created for old
classes? As an example I am referring to the QSettings moved away
thread which contained the suggestion of some sort of dumping ground
add-on.
Qt Misc
Qt Kitchen
