Re: [Interest] QWebPluginFactory + CSS
15.03.2012, 04:38, Tibo W tibo_...@yahoo.com: Hi, I'm creating an object (inheriting from QWidget) through a QWebPluginFactory. I then use CSS to modify the width and height of this object. So from c++, how can I retrieve the size I set through CSS ? width() and height() seem to return the size of the top window. QWebElement::geometry()? -- Regards, Konstantin ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Submitting bugs to Centos/RHEL ?
Onsdag 14. mars 2012 13.17.29 skrev ext Scott Aron Bloom: Just a nit.. Im a linux user and dev, but in no way consider myself a linux guy... Just setting up a new VM, and I noticed when clicking the KDE Software Development box for install, it said Install these packages to develop QT and KDE graphical applications. The bold was added by me. Clearly someone needs to tell them its Qt not QT. Feel free to do so. Everyone can fill this kind of bug, consider it your contribution to the Qt-Project ;) Cheers Frederik Again just a nit. Scott ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] QSerialport EV_RXCHAR not emitted or catched while moving window
Hi, i have a program with : - a main thread - a serial manager thread using Qserialport i noticed that if i move the main gui the EV_RXCHAR event is not fired or cached... what's wrong? thanks, Riccardo ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Possible QMenu tear-off bug
Hi list, I just found a possible bug and couldn't find any mention of it searching via Google or the Qt bug-tracker... so unless I'm not doing something completely wrong, here's what happens (sample code attached, derived from the official Qt example 'menus', extended with a long tear-off menu and simple enough to repro it, I guess): When a tear-off-enabled menu crosses multiple columns and the tear-off handle is activated, the independent window goes haywire and gets resized until its limits. Qt even spits out this message several times: QWidget::setMinimumSize: (/QTornOffMenu) The largest allowed size is (16777215,16777215) Which indicates it's doing something completely weird here :)... So, is this known? Am I the only one? Or am I doing something wrong here? If no (to all) I guess I should file a Qt bug... Note that I'm using Qt 4.8.0 on Linux x86_64, and I was informed of the problem by someone on Windows, also using Qt 4.8.0... so it doesn't seem to be a platform-specific issue. Thanks for your time, René qt-menu-tear-off-bug.tar.bz2 Description: application/bzip-compressed-tar ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QSerialport EV_RXCHAR not emitted or catched while moving window
the serial port class is this one:
http://www.google.it/url?sa=trct=jq=esrc=ssource=webcd=1ved=0CCwQFjAAurl=http%3A%2F%2Fgitorious.org%2Finbiza-labs%2Fqserialportei=8OhhT_vNGY6KhQeg6tieCAusg=AFQjCNF7vwKcu_dJz8y-QE6ziYhoPe4uNwsig2=adTbs9FuJPYZhrNXtnfALg
it expect a EV_RXCHAR event on receiving something on the serial port
so it reimplements the QWidget event function:
bool WinSerialPortEngine::event(QEvent *e)
{
// qDebug()event e e-type();
bool ret = false;
if (e-type() == QEvent::WinEventAct) {
if (EV_ERR m_currentMask m_setMask) {
m_parent-canErrorNotification();
ret = true;
}
if (EV_RXCHAR m_currentMask m_setMask)
{
m_parent-canReadNotification();
ret = true;
}
//FIXME: This is why it does not work?
if (EV_TXEMPTY m_currentMask m_setMask) {
m_parent-canWriteNotification();
ret = true;
}
}
else
{
ret = QWinEventNotifier::event(e);
}
::WaitCommEvent(m_descriptor, m_currentMask, m_ov);
return ret;
}
the problem is that while receiving events like the
QEvent::NonClientAreaMouseButtonPres on the gui thread it stop
receivng EV_RXCHAR event on the serial port class
Il 15 marzo 2012 12:53, Samuel Gaist samuel.ga...@edeltech.ch ha scritto:
On 15 mars 2012, at 12:37, Riccardo Roasio wrote:
Hi,
i have a program with :
- a main thread
- a serial manager thread using Qserialport
i noticed that if i move the main gui the EV_RXCHAR event is not fired
or cached...
what's wrong?
thanks,
Riccardo
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Hi,
With so few information, we won't be really be able to help you.
But here is a few questions:
- How is your serial manager thread implemented ? (My guess: run
reimplementation)
- Do you have signals slots directly connected ?
Hope this helps
Samuel
PS:
Did you also read this article ?
http://labs.qt.nokia.com/2010/06/17/youre-doing-it-wrong/
And there where a few discussions on the qt-nokia mailing list last year
about threading, you might want to look for them
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QSerialport EV_RXCHAR not emitted or catched while moving window
I must say, I don't understand your use of QSerialPort.
You are waiting on data coming from the serial port, aren't you ?
So, why not just connect to the readyRead signal ?
On 15 mars 2012, at 14:07, Riccardo Roasio wrote:
the serial port class is this one:
http://www.google.it/url?sa=trct=jq=esrc=ssource=webcd=1ved=0CCwQFjAAurl=http%3A%2F%2Fgitorious.org%2Finbiza-labs%2Fqserialportei=8OhhT_vNGY6KhQeg6tieCAusg=AFQjCNF7vwKcu_dJz8y-QE6ziYhoPe4uNwsig2=adTbs9FuJPYZhrNXtnfALg
it expect a EV_RXCHAR event on receiving something on the serial port
so it reimplements the QWidget event function:
bool WinSerialPortEngine::event(QEvent *e)
{
// qDebug()event e e-type();
bool ret = false;
if (e-type() == QEvent::WinEventAct) {
if (EV_ERR m_currentMask m_setMask) {
m_parent-canErrorNotification();
ret = true;
}
if (EV_RXCHAR m_currentMask m_setMask)
{
m_parent-canReadNotification();
ret = true;
}
//FIXME: This is why it does not work?
if (EV_TXEMPTY m_currentMask m_setMask) {
m_parent-canWriteNotification();
ret = true;
}
}
else
{
ret = QWinEventNotifier::event(e);
}
::WaitCommEvent(m_descriptor, m_currentMask, m_ov);
return ret;
}
the problem is that while receiving events like the
QEvent::NonClientAreaMouseButtonPres on the gui thread it stop
receivng EV_RXCHAR event on the serial port class
Il 15 marzo 2012 12:53, Samuel Gaist samuel.ga...@edeltech.ch ha scritto:
On 15 mars 2012, at 12:37, Riccardo Roasio wrote:
Hi,
i have a program with :
- a main thread
- a serial manager thread using Qserialport
i noticed that if i move the main gui the EV_RXCHAR event is not fired
or cached...
what's wrong?
thanks,
Riccardo
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Hi,
With so few information, we won't be really be able to help you.
But here is a few questions:
- How is your serial manager thread implemented ? (My guess: run
reimplementation)
- Do you have signals slots directly connected ?
Hope this helps
Samuel
PS:
Did you also read this article ?
http://labs.qt.nokia.com/2010/06/17/youre-doing-it-wrong/
And there where a few discussions on the qt-nokia mailing list last year
about threading, you might want to look for them
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QSerialport EV_RXCHAR not emitted or catched while moving window
Sorry..so what you think i have do do?
Il 15 marzo 2012 14:26, Samuel Gaist samuel.ga...@edeltech.ch ha scritto:
I must say, I don't understand your use of QSerialPort.
You are waiting on data coming from the serial port, aren't you ?
So, why not just connect to the readyRead signal ?
On 15 mars 2012, at 14:07, Riccardo Roasio wrote:
the serial port class is this one:
http://www.google.it/url?sa=trct=jq=esrc=ssource=webcd=1ved=0CCwQFjAAurl=http%3A%2F%2Fgitorious.org%2Finbiza-labs%2Fqserialportei=8OhhT_vNGY6KhQeg6tieCAusg=AFQjCNF7vwKcu_dJz8y-QE6ziYhoPe4uNwsig2=adTbs9FuJPYZhrNXtnfALg
it expect a EV_RXCHAR event on receiving something on the serial port
so it reimplements the QWidget event function:
bool WinSerialPortEngine::event(QEvent *e)
{
// qDebug()event e e-type();
bool ret = false;
if (e-type() == QEvent::WinEventAct) {
if (EV_ERR m_currentMask m_setMask) {
m_parent-canErrorNotification();
ret = true;
}
if (EV_RXCHAR m_currentMask m_setMask)
{
m_parent-canReadNotification();
ret = true;
}
//FIXME: This is why it does not work?
if (EV_TXEMPTY m_currentMask m_setMask) {
m_parent-canWriteNotification();
ret = true;
}
}
else
{
ret = QWinEventNotifier::event(e);
}
::WaitCommEvent(m_descriptor, m_currentMask, m_ov);
return ret;
}
the problem is that while receiving events like the
QEvent::NonClientAreaMouseButtonPres on the gui thread it stop
receivng EV_RXCHAR event on the serial port class
Il 15 marzo 2012 12:53, Samuel Gaist samuel.ga...@edeltech.ch ha scritto:
On 15 mars 2012, at 12:37, Riccardo Roasio wrote:
Hi,
i have a program with :
- a main thread
- a serial manager thread using Qserialport
i noticed that if i move the main gui the EV_RXCHAR event is not fired
or cached...
what's wrong?
thanks,
Riccardo
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Hi,
With so few information, we won't be really be able to help you.
But here is a few questions:
- How is your serial manager thread implemented ? (My guess: run
reimplementation)
- Do you have signals slots directly connected ?
Hope this helps
Samuel
PS:
Did you also read this article ?
http://labs.qt.nokia.com/2010/06/17/youre-doing-it-wrong/
And there where a few discussions on the qt-nokia mailing list last year
about threading, you might want to look for them
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QSerialport EV_RXCHAR not emitted or catched while moving window
Again: use the readyRead signal ?
http://qt-project.org/doc/qt-4.8/qiodevice.html#readyRead
On 15 mars 2012, at 14:27, Riccardo Roasio wrote:
Sorry..so what you think i have do do?
Il 15 marzo 2012 14:26, Samuel Gaist samuel.ga...@edeltech.ch ha scritto:
I must say, I don't understand your use of QSerialPort.
You are waiting on data coming from the serial port, aren't you ?
So, why not just connect to the readyRead signal ?
On 15 mars 2012, at 14:07, Riccardo Roasio wrote:
the serial port class is this one:
http://www.google.it/url?sa=trct=jq=esrc=ssource=webcd=1ved=0CCwQFjAAurl=http%3A%2F%2Fgitorious.org%2Finbiza-labs%2Fqserialportei=8OhhT_vNGY6KhQeg6tieCAusg=AFQjCNF7vwKcu_dJz8y-QE6ziYhoPe4uNwsig2=adTbs9FuJPYZhrNXtnfALg
it expect a EV_RXCHAR event on receiving something on the serial port
so it reimplements the QWidget event function:
bool WinSerialPortEngine::event(QEvent *e)
{
// qDebug()event e e-type();
bool ret = false;
if (e-type() == QEvent::WinEventAct) {
if (EV_ERR m_currentMask m_setMask) {
m_parent-canErrorNotification();
ret = true;
}
if (EV_RXCHAR m_currentMask m_setMask)
{
m_parent-canReadNotification();
ret = true;
}
//FIXME: This is why it does not work?
if (EV_TXEMPTY m_currentMask m_setMask) {
m_parent-canWriteNotification();
ret = true;
}
}
else
{
ret = QWinEventNotifier::event(e);
}
::WaitCommEvent(m_descriptor, m_currentMask, m_ov);
return ret;
}
the problem is that while receiving events like the
QEvent::NonClientAreaMouseButtonPres on the gui thread it stop
receivng EV_RXCHAR event on the serial port class
Il 15 marzo 2012 12:53, Samuel Gaist samuel.ga...@edeltech.ch ha scritto:
On 15 mars 2012, at 12:37, Riccardo Roasio wrote:
Hi,
i have a program with :
- a main thread
- a serial manager thread using Qserialport
i noticed that if i move the main gui the EV_RXCHAR event is not fired
or cached...
what's wrong?
thanks,
Riccardo
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Hi,
With so few information, we won't be really be able to help you.
But here is a few questions:
- How is your serial manager thread implemented ? (My guess: run
reimplementation)
- Do you have signals slots directly connected ?
Hope this helps
Samuel
PS:
Did you also read this article ?
http://labs.qt.nokia.com/2010/06/17/youre-doing-it-wrong/
And there where a few discussions on the qt-nokia mailing list last year
about threading, you might want to look for them
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QSerialport EV_RXCHAR not emitted or catched while moving window
Hi Riccardo,
Is this running on Windows? I seem to remember that the timers had the same
problem - the events don't get delivered while the window is in resize mode.
I never found a fix or workaround for this, and had to implement my own
timers in a separate thread looping on sleep.
Hope that helps,
Tony.
Sent: Friday, 16 March 2012 12:45 AM
Again: use the readyRead signal ?
http://qt-project.org/doc/qt-4.8/qiodevice.html#readyRead
On 15 mars 2012, at 14:27, Riccardo Roasio wrote:
Sorry..so what you think i have do do?
Il 15 marzo 2012 14:26, Samuel Gaist samuel.ga...@edeltech.ch ha
scritto:
I must say, I don't understand your use of QSerialPort.
You are waiting on data coming from the serial port, aren't you ?
So, why not just connect to the readyRead signal ?
On 15 mars 2012, at 14:07, Riccardo Roasio wrote:
the serial port class is this one:
http://www.google.it/url?sa=trct=jq=esrc=ssource=webcd=1ved=
0C
CwQFjAAurl=http%3A%2F%2Fgitorious.org%2Finbiza-
labs%2Fqserialporte
i=8OhhT_vNGY6KhQeg6tieCAusg=AFQjCNF7vwKcu_dJz8y-
QE6ziYhoPe4uNwsig2
=adTbs9FuJPYZhrNXtnfALg
it expect a EV_RXCHAR event on receiving something on the serial
port so it reimplements the QWidget event function:
bool WinSerialPortEngine::event(QEvent *e) {
// qDebug()event e e-type();
bool ret = false;
if (e-type() == QEvent::WinEventAct) {
if (EV_ERR m_currentMask m_setMask) {
m_parent-canErrorNotification();
ret = true;
}
if (EV_RXCHAR m_currentMask m_setMask)
{
m_parent-canReadNotification();
ret = true;
}
//FIXME: This is why it does not work?
if (EV_TXEMPTY m_currentMask m_setMask) {
m_parent-canWriteNotification();
ret = true;
}
}
else
{
ret = QWinEventNotifier::event(e);
}
::WaitCommEvent(m_descriptor, m_currentMask, m_ov);
return ret;
}
the problem is that while receiving events like the
QEvent::NonClientAreaMouseButtonPres on the gui thread it stop
receivng EV_RXCHAR event on the serial port class
Il 15 marzo 2012 12:53, Samuel Gaist samuel.ga...@edeltech.ch ha
scritto:
On 15 mars 2012, at 12:37, Riccardo Roasio wrote:
Hi,
i have a program with :
- a main thread
- a serial manager thread using Qserialport
i noticed that if i move the main gui the EV_RXCHAR event is not
fired or cached...
what's wrong?
thanks,
Riccardo
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Hi,
With so few information, we won't be really be able to help you.
But here is a few questions:
- How is your serial manager thread implemented ? (My guess: run
reimplementation)
- Do you have signals slots directly connected ?
Hope this helps
Samuel
PS:
Did you also read this article ?
http://labs.qt.nokia.com/2010/06/17/youre-doing-it-wrong/
And there where a few discussions on the qt-nokia mailing list last
year about threading, you might want to look for them
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
[Interest] QGraphicsScene mouse move event
Hi,
Quick question about QGraphicsScene::mouseMoveEvent(...):
I only receive a mouse move event when the left mouse button is
pressed. For example, this code:
void MyScene::mouseMoveEvent(QGraphicsSceneMouseEvent *event)
{
qDebug() Scene mouse move event;
if (!something)
{
QGraphicsScene::mouseMoveEvent(event);
return;
}
// Do somehting each time the mouse moves over the scene rect.
}
prints Scene mouse move event only when I press the left mouse button
and move the mouse.
Is this normal behavior? Should I reimplement the mouseMoveEvent from
QGraphicsView instead? This is kinda strange...
Regards,
Marc
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QGraphicsScene mouse move event
Tony Rietwyk t...@rightsoft.com.au writes: Hi Marc, Have a look at QWidget.setMouseTracking. Aaaah of course! Thanks, Marc ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] qt5 shapshot - not git or guitorious
I am looking for a snapshot of Qt5 but not from git or guitorius do to the fact that git does not work through proxies, or rather, the proxy setup where I am at. Talking about http_proxy and the like is off-topic. Been there and for various reasons, it won't work FOR_ME. So I am looking for a snapshot of Qt5. The thing is if I were to use the snapshot from gitorious, it breaks and times out, not to mention that grabbing qt5 only gets the top level and not the subdirs. So where can I get a source snapshot, old school style? ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QSerialport EV_RXCHAR not emitted or catched while moving window
Date: Fri, 16 Mar 2012 01:30:15 +1100 From: Tony Rietwyk t...@rightsoft.com.au Is this running on Windows? I seem to remember that the timers had the same problem - the events don't get delivered while the window is in resize mode. I never found a fix or workaround for this, and had to implement my own timers in a separate thread looping on sleep. I've experienced the same symptom (but was not able to diagnose why) using both QSerialPort and QExtSerialPort. If the window was dragged extensively, data loss would occur (characters would be unrecoverably lost). But the serial protocol had disabled any form of flow control (e.g. XON/XOFF, or hardware). So I blamed the problem on using a fragile serial protocol. Was this correct? If not, how are we supposed to use QSerialPort / QExtSerialPort reliably in a GUI app? Thanks, David ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Possible QMenu tear-off bug
Reproduced it here on Debian testing amd64 with Qt 4.7.4 — opened the Tear off menu, clicked the very top item and... got a decoration-less (and thus nearly uncontrollable) opaque black window occupying ~90% of the screen and with right and bottom sides somewhere beyond desktop edges. On 03/15/2012 04:43 PM, R. Reucher wrote: Hi list, I just found a possible bug and couldn't find any mention of it searching via Google or the Qt bug-tracker... so unless I'm not doing something completely wrong, here's what happens (sample code attached, derived from the official Qt example 'menus', extended with a long tear-off menu and simple enough to repro it, I guess): When a tear-off-enabled menu crosses multiple columns and the tear-off handle is activated, the independent window goes haywire and gets resized until its limits. Qt even spits out this message several times: QWidget::setMinimumSize: (/QTornOffMenu) The largest allowed size is (16777215,16777215) Which indicates it's doing something completely weird here :)... So, is this known? Am I the only one? Or am I doing something wrong here? If no (to all) I guess I should file a Qt bug... Note that I'm using Qt 4.8.0 on Linux x86_64, and I was informed of the problem by someone on Windows, also using Qt 4.8.0... so it doesn't seem to be a platform-specific issue. Thanks for your time, René signature.asc Description: OpenPGP digital signature ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Possible QMenu tear-off bug
On Thursday 15 March 2012 18:56:48 Constantin Makshin wrote: Reproduced it here on Debian testing amd64 with Qt 4.7.4 — opened the Tear off menu, clicked the very top item and... got a decoration-less (and thus nearly uncontrollable) opaque black window occupying ~90% of the screen and with right and bottom sides somewhere beyond desktop edges. Thanks for reproducing the issue! I've now filed a bug (after checking again that there's really no equivalent bug already reported): https://bugreports.qt-project.org/browse/QTBUG-24815 Regards, René ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] qt5 shapshot - not git or guitorious
On 15.03.12 10:01:30, Jason H wrote: I am looking for a snapshot of Qt5 but not from git or guitorius do to the fact that git does not work through proxies, or rather, the proxy setup where I am at. Talking about http_proxy and the like is off-topic. Been there and for various reasons, it won't work FOR_ME. So I am looking for a snapshot of Qt5. The thing is if I were to use the snapshot from gitorious, it breaks and times out, not to mention that grabbing qt5 only gets the top level and not the subdirs. So where can I get a source snapshot, old school style? The Gitorious Website provides links to download the repository as tar.gz. You'd have to download the individual components though and combine them manually. Andreas ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] qt5 shapshot - not git or guitorious
That feature doesn't work properly. It dies, and you end up getting a partial, corrupt archive. From: Andreas Pakulat ap...@gmx.de To: interest@qt-project.org Sent: Thursday, March 15, 2012 3:25 PM Subject: Re: [Interest] qt5 shapshot - not git or guitorious On 15.03.12 10:01:30, Jason H wrote: I am looking for a snapshot of Qt5 but not from git or guitorius do to the fact that git does not work through proxies, or rather, the proxy setup where I am at. Talking about http_proxy and the like is off-topic. Been there and for various reasons, it won't work FOR_ME. So I am looking for a snapshot of Qt5. The thing is if I were to use the snapshot from gitorious, it breaks and times out, not to mention that grabbing qt5 only gets the top level and not the subdirs. So where can I get a source snapshot, old school style? The Gitorious Website provides links to download the repository as tar.gz. You'd have to download the individual components though and combine them manually. Andreas ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] qt5 shapshot - not git or guitorious
On 03/15/2012 10:01 AM, Jason H wrote: I am looking for a snapshot of Qt5 but not from git or guitorius do to the fact that git does not work So where can I get a source snapshot, old school style? Jason: If you can wait for snail-mail, I can burn a CD (or DVD, if the total size requires one). If that sounds good, reply with your mailing address privately-- and be sure to put the word cuty-five-point-something (wink) in your title. This is a "live" email address, but my spam filters are pretty tough. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QTableWidget performance
Hi. Thanks for the reply. later. The proper answer to this is that you need to run this through a profiler. You know, premature optimization... If your code runs on Linux, you should take a look at KCacheGrinder. Indeed, and this has been mentioned by someone else on the team... right now, it's just an issue of time. Lots of important stuff on the table. Impossible to answer, when you don't know what the problem is. I *really* don't like the *Widget versions, and will always tell my customers to go with a proper model (not a QStandardItemModel based), but that's for other reasons. I will be looking into Model/View for future projects, but *most* stuff until now is a rather small set of data, that changes somewhat rapidly, and from different sources. Definitely beyond the scope of this email. My main resistance to this is that while the data is somewhat simple, I already have a pretty complex system to filter what should be displayed and what shouldn't, what colors should be displayed for visible items, what font to use, and whether a sound should be played or not. This is all configured by the user in the GUI. Aha, that might very well be the reason. You should try and remove the filter code completely and see if this solves the problem. Those filters can be very expensive to calculate. The checks themselves are pretty light (usually boolean or an integral comparison). The actions are another story, but even then, it's almost always a cell coloration. But, for this particular instance I was checking, he has just a plain vanilla view. No checks, no colors, no sounds, no nothing... just lag. :/ The main difference is hardware, and the Window Manager. My guess is it's hardware. I think we'll upgrade first and then revisit the problem. :) -Paul ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
