General and Desktop

Glad to hear the problem is solved. You can "close" the thread by editing your very first post and add "[Solved]" to the beginning of the subject.

Oh sherbert sorry - i copied and pasted my code without thinking. This was me just playing around to see if i can try and sort the problem. But i see rokemoon has helped with the size problem.. I'll try that - thanks!!

Yes, you can get hold of the internal layout of the QMainWindow by calling layout() on it.

[quote author="mehoggan" date="1313658650"]Okay thanks for the input. So this behaves "somewhat" like MFC, in the since that the message pump and the WinMain site inside a DLL. Thank you for the clarification.[/quote] yep The message pump is your qApp->exec() call.

Thanks again for the reply, I've moved the ::open(..)/::close(...) calls to a class outside my capture class (so doesn't inherit from Qthread) and now the close call is executing correctly. Don't really understand that but maybe I'll revisit one day! Thanks for the QImage buffer tip, I need to pick up as many of these as I can now...

You can set the items in the even columns to read only like this: @ QTableWidgetItem *twItem = tableWidget->item(3, 4); twItem->setFlags(Qt::ItemIsEnabled | Qt::ItemIsSelectable); // if you do not need selectable items this is ok: twItem->setFlags(Qt::NoItemFlags); @ Or set the flags during creation of the items, of course.

i solved it with the following code. @QMainWindow::centralWidget()->layout()->setContentsMargins(0,0,0,0);@

may be you can try setVerticalScrollBarPolicy() setHorizontalScrollBarPolicy().

Thanks, I will try that!

I don't know if I made myself clear, but if you need further help, just ask.

Kaohnig and Volker hit the nail on the head. Because npts was only an int, the computation was downcast regardless of the type I assigned to nrows. Since I can't change the type of npts (it comes from other code... I showed it adjacent for clarity in my post), I had to recast it during the nrows computation: @int npts = 71338; quint64 nrows = quint64(npts) * ( quint64(npts) - 1 ); //5089038906 as expected@ Thanks for the help! I knew it was something obvious.

Try QGraphisPixmapItem: "http://doc.qt.nokia.com/4.7/qgraphicspixmapitem.html#details":http://doc.qt.nokia.com/4.7/qgraphicspixmapitem.html#details The easiest way: You can set the scale of the QGraphicsView: "http://doc.qt.nokia.com/4.7/qgraphicsview.html#scale":http://doc.qt.nokia.com/4.7/qgraphicsview.html#scale The "scale" method uses two factors, one for X and another for Y. As I understand, you will always keep the Y factor as 1.0 . But before setting a new scale (a particular case of transformation), you will need to reset the previous transformation: "http://doc.qt.nokia.com/4.7/qgraphicsview.html#resetTransform":http://doc.qt.nokia.com/4.7/qtransform.html#scale A bit more complicated, as that might be a little bit more slower than really understanding the transformations and applying a calculated one, adjusted for the difference in scale, rather than reseting and setting a new one. Create a QTransform and apply to it the scale you need: "http://doc.qt.nokia.com/4.7/qtransform.html#scale":http://doc.qt.nokia.com/4.7/qtransform.html#scale Then apply it to the QGraphicsView without combining it with the previous transformation: "http://doc.qt.nokia.com/4.7/qgraphicsview.html#setTransform":http://doc.qt.nokia.com/4.7/qgraphicsview.html#setTransform Your resize event might do this: get new width; calculate the ratio between this and the first ever width; create a QTransform object and set its scale properly; apply this to the QGraphicsView using its setTransform method without combination to the previous; OR get new width; calculate the ratio between this and the last one; save width for future use; create a QTransform object and set its scale properly; apply this to the QGraphicsView using its setTransform method combining it to the previous; I have never tried to do this, but I guess that will work as expected. Hope this helps, Francisco

Well, after tinkering with it, I was able to get signals and slots to essentially do what I want. I'll mark this as solved.

Qt is big, but pretty easy when you start getting a hang of it... To just understand what you can do with a layout, simply add a QVBoxLayout to your mainLayout, and add some buttons to it, something like this (where the first two lines are already in your code): @ QHBoxLayout *mainLayout = new QHBoxLayout; mainLayout->addWidget(glWidget); QVBoxLayout *vLayout = new QVBoxLayout; mainLayout->addLayout(vLayout); QPushButton *button1 = new QPushButton("Button 1"); vLayout->addWidget(button1); QPushButton *button2 = new QPushButton("Button 2"); vLayout->addWidget(button2); vLayout->addStretch(); @

I see. Maybe they could find a way to make it all a bit less trouble though. No worries though. I seem to have it working OK now and I can get on with my project. Thanks for the help.

It work thank you

Thanks for this - I think i'll use QWidget instead of QDialog as a parent class. However, i have managed to get it working but the size is just a little weird. It cuts off 3 quarters of my dialog window so i have to manually resize this each time the app is run. I'm hoping that using QWidget instead of QDialog will sort this..

[quote author="Andre" date="1313579823"]Personally, I dislike global variables. I find there are really no good use cases for them. What you can do instead, is use QApplication to hold your application wide data. You can either: Subclass QApplication, and give it proper access methods to your data, or Use Qt' s dynamic property feature to just set a QVariant property on your QApplication object However, it is just a personal dislike. The language supports it (and Qt does nothing that constrains your use of it), so go right ahead if you must. [/quote] Andre, you are raising certainly a valid point with your response. Global variables have always some "smell" of the old "FORTRAN common block". Hard to controll because completely confusing when you are looking for the place changing some part of your data. One must have no other alternative when using global variables. Otherwise they may be the start of disaster.

"untranslated string as additional itemData" seems to be better option. i will give it a try. Thanks