I have QDialog with
setWindowFlags(Qt::Popup | Qt::FramelessWindowHint);
and it displays just fine (with shadow and all).
However my nativeEvent handler is never called with the WM_NCHITTEST
message. It is called with WM_LBUTTONDOWN and others. When I replace
Qt::Popup with Qt::Dialog the
Muhammad Bashir Al-Noimi schreef op 21-1-2014 18:22:
Howdy,
I'm using QTableView in very basic mode to view a QSqlTableModel but one
of numeric column shows the numbers using 'e' factor while they should
be in digits only '100'
How can I change the format of specific column
Constantin Makshin schreef op 21-1-2014 18:48:
There's no real need to use debug version of Qt if you don't want to
debug Qt itself, so in most cases the programmer won't see that warning.
Disagree there. There is every reason to run debug application code
against debug Qt libraries. If only
Le 21/01/2014 18:48, Constantin Makshin a écrit :
There's no real need to use debug version of Qt if you don't want to debug Qt
itself, so in most
cases the programmer won't see that warning.
Sorry, but I strongly disagree with that... sometimes when facing a bug or
some strange,
To follow André and Yves:
- If you debug code within signal/slots or event mechanisms for instance,
it's very handy to trace through Qt code. In Qt, your code is often called
by Qt's classes.
- It also activates many Q_ASSERT checks, for instance with out-of-bounds
indices. With release qt libs,
I've got a custom menu item (ColumnLayout-based), where the items inside
are some custom button items. Each item is set up with KeyNavigation so
that active focus is moved up and down using the cursor keys.
If a button item's enabled property is set to false while having active
focus, it's not
Jason asketh:
Is there a Qt way of getting a handle for a running windows process(or
just checking if a certain .exe is currently executing) and determining
how long it has been running?
Bo respondeth:
No, this isn't something you can do in Qt. You have to do platform
specific code
On Tue, 2014-01-21 at 16:40 +0100, Frederik Gladhorn wrote:
Tirsdag 21. januar 2014 15.41.40 skrev Cornelius Hald:
Hi,
I'm trying to set an application wide cursor for some time and later
return to the default cursor.
I've tried
Thank you Bo and Charley.
- - - - - - - - - - - - - - - - - - - - - - -
Jason R. Kretzer
Application Developer
Google # 606-887-9011
Cell # 606-792-0079
ja...@gocodigo.commailto:ja...@gocodigo.com
“quidquid latine dictum sit altum videtur”
[cid:image001.png@01CECA4D.CA4030A0]
On Jan 22, 2014,
Onsdag 22. januar 2014 13.46.03 skrev Ola Røer Thorsen:
I've got a custom menu item (ColumnLayout-based), where the items inside
are some custom button items. Each item is set up with KeyNavigation so
that active focus is moved up and down using the cursor keys.
If a button item's enabled
Hi
I'm writing a data-intensive application which must wait for large chunks
of data from a remote database, sometimes about 10 seconds. So I want to
keep UI in main thread (which one is running event loop) and move all data
operations to other threads. I can see how to connect signals/slots from
Your database class uses a std::recursive_mutex (not the Qt mutex, its a
resource waster!) to synchronize access to the database.
Then in the method that returns a new shared pointer of QSqlDatabase you
use a std::lock_guard with that mutex to allow only one thread to use the
DB. I usually also
On quarta-feira, 22 de janeiro de 2014 10:29:42, André Somers wrote:
Disagree there. There is every reason to run debug application code
against debug Qt libraries. If only because it enables asserts that
catch programming mistakes
There aren't many of those. The Qt front-end API does not
On quarta-feira, 22 de janeiro de 2014 16:39:24, Philipp Kursawe wrote:
Your database class uses a std::recursive_mutex (not the Qt mutex, its a
resource waster!)
Do you have any numbers? QMutex is very small and optimised (on Linux).
QWaitCondition suffers because QMutex is so small.
--
On quarta-feira, 22 de janeiro de 2014 18:48:53, Soroush Rabiei wrote:
A connection can only be used from within the thread that created it.
Moving connections between threads or creating queries from a different
thread is not supported.
My question is how can I make connections between UI and
The Win32 implementation uses a mutex, which is used for inter-process
sync. Inside a process its a waste. Better use CriticalSection, its a
kernel object and several times faster then a mutex on Win32.
On Wed, Jan 22, 2014 at 4:45 PM, Thiago Macieira
thiago.macie...@intel.comwrote:
On
On quarta-feira, 22 de janeiro de 2014 16:52:22, Philipp Kursawe wrote:
The Win32 implementation uses a mutex, which is used for inter-process
sync. Inside a process its a waste. Better use CriticalSection, its a
kernel object and several times faster then a mutex on Win32.
I'm sorry, but the
Hello Oliver,
Am Mittwoch, 22. Januar 2014, 08:21:11 schrieb Till Oliver Knoll:
Am 21.01.2014 um 20:25 schrieb Petric Frank pfr...@gmx.de:
...QGraphicsWigdet. Only texts (w/ reduced HTML) can be
passed to the setTooltip method.
The class i meant QGraphicsItem, not QGraphicsWidget - my
Hello,
i've got it to use it with a QLabel. For the records (Qt 5.2.0) here is
example code (ui-label is of type QPixmap* ):
- cut ---
QPixmap pixmap;
... some drawing tasks ...
QByteArray byteArray;
QBuffer buffer(byteArray);
pixmap.save(buffer,
On quarta-feira, 22 de janeiro de 2014 22:01:39, Philipp Kursawe wrote:
sorry got that mixed up. Qt uses Events under Windows (was that changed in
Qt5?), which is still not as efficient as CriticalSections.
Yes, QMutex got a large rewrite in Qt 5.
I'd like to see your benchmarks. This is what
Hello list... I'm new here, so be gentle ;)
I have a question that was posted to the Qt forums here:
http://qt-project.org/forums/viewthread/37413/
I learned some things there, but was also directed here for more wisdom.
Here's as brief a summary as I can muster... see the posting for
Ah that explains it! Thanks for the benchmarks. We only tested it with the
old 4.8 implementation and decided to go with std::mutex instead. We might
check out QMutex again!
Does it support the behaviour of std::recursive_mutex?
On Wed, Jan 22, 2014 at 11:16 PM, Thiago Macieira
On quinta-feira, 23 de janeiro de 2014 05:54:36, Philipp Kursawe wrote:
Does it support the behaviour of std::recursive_mutex?
What behaviour, in specific?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
23 matches
Mail list logo
