General and Desktop

Gerolf, In the editing config files are you suppose to add the bold lines in or replace the existing lines in the config files? Also, what does the "..." in "LFLAGS = -static -static-libgcc …" mean, is to represent that there should something after it? Thanks

Hi Paolo, just as a side note: all QObjects arte copy disabled. Only the data containers (strings, containers, variant, ...) are copy enabled. This is by design, as widgets are typically created by new, not by assignment. This is also necassary as the parent child relation ship comes also into the game. Think of a QMainWindow with a huge UI insid (many child widgets with child widgets with ...). Copying that will be really complicated, especially as the parent only has a QWidget pointer but the cchild is a QWidget derived class...

Glad to hear it is resolved.

well, exploring a bit, I've discovered the problem is inside qt. Since I have no time (and probably not enough skills) to remake the qsqlrelationalmodel class I'm stopping to use it and handle it by hand. when everything would be stable, I will post in the wiki my code snippets, and I hope it would be useful to somebody. Paolo

for while I created little complex network of signals emited from closeEvent() overloaded methods, and slots to close each other window in it's own manner with confirmation to main window, looks like all works fine

Turns out that it wasn't a push_back error. I got debugging running and discovered that I was trying to call parts of a QVector that didn't exist, elsewhere in the code. My file reader wasn't working because it couldn't find the input file, so it was kicking out of the reader. Now I need to go home and figure out where in the code I'm accessing non-existent entities of a QVector. Thanks for all the suggestions and your patience guys. I figure that eventually I'll know enough to do this programming thing without the aid of others. Until then, I'll be asking colleagues at work and posting to forums.

Thanks, I mixed that up. So I also could comment the connect line, its not more needed fopr this purpose. Works!

Ok, thanks for clarifying that it's much appreciated. I'll also do abit of extra reading myself from links you provided.

another option would be to check if the file you want to open exists before trying to open it. Just use something like @if(QFile::exists(filename)) { QFile file (filename); if(file.open(QIODevice::ReadOnly) { QByteArray strFileContent = file.readAll(); } }@ This way its easier to find the error when debugging. PS: Any possible errors are mine and are not to be used by anyone else.

There is no prepackaged windows build for x86_64 (there is no such build for x64 either, but I think you are looking for the former one), but can be built "easily":http://developer.qt.nokia.com/wiki/How_to_build_64bit_Qt_for_windows. You will find a list of available database drivers "here":http://doc.qt.nokia.com/latest/qsqldatabase.html#QSqlDatabase-3. Custom drivers can be added. You will need a DBMS that supports 64 bit, Qt does support it anyways. It is Qt, not QT.

Well it appears that this is not what it seems! The issue lies with the timed locking of the file for output! I'll look into it a bit more to see if I've made a screaming error and post back with an update. Thanks for reading.

[quote author="peppe" date="1311579226"] (In any case, you can just get the list of children widgets and call update manually).[/quote] That's exactly what I do not want to do, not smart anyway :( In GUI view, yes, I should not bother to manually update children. In my case, I have another internal logic to update view. When and how to paint view is not fully determined by those paint events.

Make use of QFileInfo. Edit: Ignore this post as I didn't refresh the page to see the above posts.

QGraphicsView, QGraphicsScene and QGraphicsViewItems could be used vector based. You can even use widgets in it, but those will remain raster based as ZapB mentioned. It uses QPrinter for output. You could check the pdf output possibilities first.

[quote author="Tobias Hunger" date="1311528408"]What kind of system are you targeting? If you are targeting a linux system: Have you tried to use the 64bit linux g++ mkspec?[/quote] It's Mac OSX 10.6. I've just succeeded to compile my codes. I made a new mkspecs named mac-g++-4 form existing mac-g++ and modified few lines by switching -arch x86_64 and -XArch_x86_64 into -m64 @ QMAKE_CFLAGS_X86_64 += -m64 -mmacosx-version-min=10.5 QMAKE_OBJECTIVE_CFLAGS_X86_64 += -m64 -mmacosx-version-min=10.5 .... QMAKE_CXXFLAGS_X86_64 += -m64 -mmacosx-version-min=10.5 QMAKE_CXXFLAGS_X86 += -m32 @

Please mark your post as [SOLVED]. Thanks.

You can't in C++. QVector3D has no virtuals, thus no virtual table nor RTTI information. You need to use other means to store that information (QVariant / QMetaType come to mind).

I've found one way that gets me part way there with flex which is to simply use the under-documented function yy_scan_string() and pass in QByteArray.constData() as the argument before calling the yyparse() function. ie: @ ... QByteArray ba = myString.toUtf8(); YY_BUFFER_STATE string_buffer = yy_scan_string( ba.constData() ); yyparse(); yy_delete_buffer(string_buffer); @ That will probably get me close enough for this little project as I am not expecting to have to worry about UTF16.

I post all code. I think what I don't need mixture OpenGL and Qt functions.