General and Desktop

[quote author="Andre" date="1322655755"] Also, I would advice against an approach as sketched by Lukas above. Don't try to create your own format for defining UI geometries, but use what's there already instead. [/quote] The example was sketched under the precondition that .ui files are not applicable. If they can, .ui files are the way to go.

[quote author="Andre" date="1322646685"]No, that is not the right approach. Painting is done from the paintevent, and I have already laid out the options you have to manipulate that. Your way is not going to work. [/quote] Actually it worked with some tweaks here and there. But there were some side-effects I didn't think of. I tried creating custom delegates, which works as expected!

Well, not getting into much details here, is it possible that you make an extra, transparent layer on your image that would be another graphics scene over your graphics scene and let the drawing occur there? Then you could just move the element from the transparent scene to your actual scene.

Thanks. I fixed it.

Hi again and thanks for the answers. I will try to implement your suggestion Volker.. I already have something similar but I hadn't thought I could use it. Thanks!

thanks pal, this is really helped me.

Thanks, I'll do that.

[quote author="Lukas Geyer" date="1322482667"]Have you tried using the OpenGL engine or setting an OpenGL viewport? @ int main(int argc, char *argv[]) { QApplication::setGraphicsSystem("opengl"); QApplication application(argc, argv); ... QDeclarativeView view; view.setViewport(new QGLWidget); } @[/quote] thanks. Yes I have tried opengl as graphic system but it doesn't support transparency. Now I use mix with native paint engine and opengl paint engine (using viewport). I hope it will work stable.

Then, why do you need it in your own application? In that case, any MDB to SQLite conversion will do, right? Even better if you can script it.

The soap action is not the mimetype, indeed. It is a string expected by the service in order to identify the action to execute. The best way to find it out is to look at the .wsdl file. In fact the whole code could be generated from the .wsdl file, using kdwsdl2cpp. Can you send me the .wsdl file? The issues with the soap version might be fixed in the most recent kdsoap, would like to try the code below and email me with the results? http://kdab.com/~dfaure/2011/kdsoap-1.1.99-r43009-source.zip

Well, if that is the case then i don't wanna disturb or annoy anyone. Maybe there are just a few who are interested in ETA's :-) But to anyone here, thanks for your support in that matter.

Can you send me the corresponding .wsdl file?

Another solution could be extend the QLabel class and create a SLOT to receive the stateChanged from QCheckBox. The connection between them could be performed with the loop located in the class constructor.

I've never seen code that used macros (#if 0 and alike) or multiline comments to disable large sections of code which wasn't just pure pain to read and understand, especially during code review sessions. It gets even worse if your are forced to use an editor which doesn't support visual suppression of disabled code. It might have its right during immediate development, but every coding guideline should strictly enforce that all disabled code has to be removed as soon as a file is commited. If it needs to be archived a versioning system is the way to go.

I'm assuming you're using traditional Qt (e.g. not QML or something). I'm not entirely sure by what you mean by "applied stylesheet through paintEvent", but perhaps I can suggest that you use a more specific CSS selector when setting the style. For example: @ QPushButton,QLabel { background: green; } @ .. will only style the QPushButton and QLabel objects Or: @ #myText { color: green; } @ .. will only style the color of objects with a QObject::objectName() of "myText". Or: @ .QWidget { background: red; } @ .. will only style objects of class QWidget but not sub-classes of QWidget Check out http://doc.qt.nokia.com/latest/stylesheet-syntax.html#selector-types for more info. Also, something I haven't seen documented, but is clearly in the code is that a property can be set to "native" (e.g. "border: native") to basically say that you want that property styled natively as if no stylesheet had been set. Apologies if I'm not understanding the question. [EDIT: code formatting, please wrap in @-tags, Volker]

Thanks - bug reported: https://bugreports.qt.nokia.com/browse/QTBUG-22929