General and Desktop

You have provided a relative file path to the ini file. My bet is that the current working directory of the running program is not what you think it is.

tnx for your help so much.

Do you want the parentWidget to remain fixed or the individual widgets(seperated by QSplitter)? the parentWidget can be fixed by setFixedSize() for the childWidgets, you need to use something else as a separator(QSplitter is meant to make resizable widgets within another widget)... There is a Vertical Line Component in Qt Designer(don't know its hard-coded equivalent, though you could use a QFrame for it)

sidewinder your are right. To print correct global string this is required: @ global.toLatin1() @

It is true. I am experimenting permformance issue. So where should I add it? ty

Well there isn't much code to show. At the moment I use this event handler just to detect when the event takes place. @ void MyWindow::closeEvent(QCloseEvent *) { qDebug() << "closed"; } @ That works fine, but the problem is, that this is just an event that takes place when I close that window. It doesn't matte how I achieve this, e.g. by using the window close button or by closing the application. The point is, when I click on the window close button (the one that is integrated in the frame) the window closes anyway. What I'm looking for is to detach this button from its behaviour. E.g. when I click on this button, something else happens (whatever I want) but it does not close the window. Edit: Exactly what Neutron Stein wrote, thx!

Thank you Ivan and Skylar. You have given me a valuable info.

No, because QButtonGroup is not a widget. However, you can add the radio buttons to the box layout, and still add those radio buttons to a QButtonGroup.

No, there is no Qt API do that. Having said that: You may be able to use platform depended API, or You could hide the default title bar, and implement your own

You can build right now yourself, or use any of the available builds out there already. Look at http://releases.qt-project.org/digia and/or http://releases.qt-project.org/qt5.0/beta-snapshots

OK, with a fresh brain I have now solved it (just in case anyone else has this problem). The projects were identical for all intents and purposes except for the ui (since I was not accessing the ui and my scroll class was the only thing on the screen I did not see that as a problem). My full project had styling applied in the UI - inc styling on the scroll bar. Remove that and bingo!!! (In my defence the whole point was to have the scroll bars hidden so I did not see the styling).

I tried it, but it does not work. I forgot to they, that I want to use it on Windows. I think it is a problem with the path. I need an absolute path, starting with /, so it seems it is Linux based.

OK, so it's basically the same idea :-) only in python one can just dynamically add id/index to the object ..

@ void QTableWidget::clear() @ The "documentation":http://qt-project.org/doc/qt-4.8/qtablewidget.html#clear is your friend :)

There are several versions of disconnect, which take different sets of arguments. Did you read the docs on all of them?

OK, Thank a lot, I see it in the docs as well now (must have been tired ...)

See http://qt-project.org/forums/viewthread/18609.

You could make a timer which triggers every 5 secs and checks whether the cursor has moved further than, for example, 2 pixels in that time (see QCursor::pos()). If it hasn't moved for n consecutive intervals, lock the application. For the keyboard it's more difficult when your program doesn't have focus. I wouldn't recommend creating keyboard hooks for this, because your program wouldn't be distinguisable from a malicious keylogger. If you just want to react to keyboard events while your application is active, look into event filters. //EDIT: Thought about it. If you're not writing a text editor or word processor, just checking the cursor position and ignoring the keyboard should be fine for your purpose. //EDIT2: If this is an industrial application (i.e. doesn't need to be pretty but robust), assign each user his own background color tone. This way a user will feel foreign when working with a different account and should notice it right away.

Thanks mburr! I did some more testing and you pinpointed the problem exactly.