General and Desktop

Holly s... what a shame ;) yeah I had QT -=gui But... I compiled it earlier on Linux without any errors. Strange. :o Thanks a lot.

No raaghuu, I am trying to making something more or less like cyber software.

I think my mousemoveevent is already lightweight because the if condtions are rarely satisfied: @void MatrixW::mouseMoveEvent(QMouseEvent *e) { if(thismove!=none) { int xnew=e->x()/larghcell; int ynew =e->y()/altcell; if((xnew!=xN||ynew!=yN)&&(xnew<size_x && ynew<size_y)) { if (isarelease) { isarelease=false; if (thismove==del) setcell(xN,yN,0); else if (thismove==add) setcell(xN,yN,1); } xN=xnew; yN=ynew; if (thismove==del) setcell(xN,yN,0); else if (thismove==add) setcell(xN,yN,1); update(); } } }@ (thismove!=none) only if the mouse is clicked ((xnew!=xN||ynew!=yN)&&(xnew<size_x && ynew<size_y)) is rarely true each 50-100 ms The good way to do this I think is to start a timer when the mouse was clicked, the timer call each 50-100ms a function like MatrixW::mouseMoveEvent(QMouseEvent *e) where the program can read the muose position. The mouse release event stop the timer. But I don't know how to read the mouse position in the function called by the timer continually read the mouse position would be the same as what I do now (about the slowdowns)

:) perfect, thank you so much!!

Cool but wouldn't all my Item inside the View been flipped as well ? as if I apply a scale(1,-1) to flip the y direction axis and then the transform to reset the origin . the "space" woulld be upside down ? would I have then to also scale(-1,1) all my childs item so they are the right way around ? I will do some test, I want to try to do it the correct way rather than "a way" that kinda works :) Thanks for your reply Damien

@ QList<int> list; QString string; ... ... ... for(int i=0; i<list.size(); i++) { string += QString::number(list[i]); if(i<list.size()-1) string += "," ; } @

No, sorry. I don't use Lion -- it has broken multi-monitor support, and as I have six monitors, I've no interest in it. Also sandboxing, certificating, etc. Lion is a regression as far as I'm concerned. I use Snow Leopard and Leopard in-house, and the errors I described here were discovered and exist under those: 10.5. and 10.6. Those are 10.6 (Snow Leopard) diagnostics in my post above. What you've managed to do, however, is confirm that the Qt bug is problematic under Lion / 10.7 as well, for which I thank you. :)

I figured out why nextId() always returns -1. The reason is that I was using the nextId() in the constructor. Before the QWizardPage being inserted into QWizard, QWizard has no reason to know which page is the next page of current page. It's a stupid mistake. Sorry for disturbance.

Thanks, I am looking for a similar solution. Since it is a table, and its validation depends on the current column, how to find the column number from the above approach? Or is it possible to similar programming for QtableView?

"you will have to use (asynchronous) signals and slots" --> Use Qt::QueuedConnection as the Qt::ConnectionType parameter of QObject::connect(...) parameter, to detach the threads.

My best idea right now is to use a composition: A QGraphicsWidget containing the item I want. The tricky part is that one essential change notification (boundingRect changes) is missing, which makes things kinda awkward.

You're right, actually. It was a statement, not a question.

No, they are read at run-time, which actually makes them somewhat slow at times.

There are two possibilites: provide a default value at database level (using a DEFAULT column constraint) provide a default value at code level, by connecting to "QSqlTableModel::primeInsert()":http://doc.qt.nokia.com/4.7-snapshot/qsqltablemodel.html#primeInsert

Find the main widget of your application. Usually, an instance is created in your main() function. Usually, it's constructor will have (lots of) stuff like: @ m_lineEdit = new QLineEdit(this); layout->addWidget(m_lineEdit); @ That is where the UI is constructed. moderator note: @ maplesyrup23, could you please edit your first post to give the post a normal title, and put the actual, complete question in the body of your message?

Another mistake are your keywords: its not "signal" and "slot" but "signals" and "slots"... Is this really the original source-code? because this shouldn't compile at all, when I try to define a signal with "signal:", I get the following compiler-error: "Not a signal or slot declaration"

The tutorial says: "<...> it is required to bind a VAO before setting up the attributes. This behavior is part of the OpenGL 3.3 core profile." Add this in initializeGL before m_shader.setAttributeBuffer: @uint vao; typedef void (APIENTRY _glGenVertexArrays) (GLsizei, GLuint); typedef void (APIENTRY *_glBindVertexArray) (GLuint); _glGenVertexArrays glGenVertexArrays; _glBindVertexArray glBindVertexArray; glGenVertexArrays = (_glGenVertexArrays) QGLWidget::context()->getProcAddress("glGenVertexArrays"); glBindVertexArray = (_glBindVertexArray) QGLWidget::context()->getProcAddress("glBindVertexArray"); glGenVertexArrays(1, &vao); glBindVertexArray(vao);@