General and Desktop

You're welcome. Keep in mind, that you are completely responsible of managing the data storage. QAbstractItemModel just provides the interface for a standardized way of accessing and setting the data, the implementation is solely up to you.

Thanks Chris!

Oh, I see. I don't think that functionality is built into QListWidget. I guess you could subclass QListView and reimplement the drag event to move the widgets around so that there was always a "hole" under the cursor.

@Andre, ouch, how could I miss that :) Thank you very much, I appreciate your help :)

Putting widgets in there is even more expensive, and harder to manage. I used QTextDocument::drawContents(), and kept the textdocuments in a cache.

Ah I found this: Ant Farmer (181 points) : can tag (while were in Open Beta all ranks can tag) and add doc notes

First: make your code readable. The indenting is a complete mess. Blocks of code at the same level (if, loops) should be aligned at the same level. Your code to check whether an item is in the list, is broken. If you have 10 items in the list, you add the incoming string 9 times. I would suggest to use QListWidget's findItems() method to check for the existence of an item. The construction of your msg QString is suboptimal. You construct a default empty string and assign a newly created string afterwards. This is better: @ QString msg(datagram); @ Note, that QString has a constructor taking a QByteArray, there's no need to use the const char data pointer of the array. Did you check that msg contains a proper string?

i solved this post. i had to remove the line QStringList userselect; from the mainwindow.cpp file. sorry for this inconvenience.

This is not a bug, I figured out why after looking at the MDI example. I need to call SubWindow->show() after I add it to the mdi area.

AH! Your'e right then, that's exactly what I want: I didn't understand that the eventFilter() was happening BEFORE the event made its way to the QLineEdit, I thought it was something I had to implement IN the QLineEdit. Awesome, thanks for the clarification.

Have you tried checking the return value (it's a boolean, I believe), and if false checking lastError() to see if it contains info about the failure?

Ok I think it is not the first time I do not express correctly what I am trying to do. I edited the first post. Tell me if it is not clear.

QFile::resize(0).

[quote author="Gerolf" date="1323954896"] AFAIK the debug msvcrt* files are not allowed to distribute. (MS license)[/quote] This is true and it is clearly stated in readme file.

Thank you for your answer!

if the login details are ok, send a signal that connects to some slot that creates + shows the logged.ui form, and then hide() the mainwindow [code] void mainwindow::tryLogin( /* some details */) { bool login_is_ok = some_checking_method(/details/); if (login_is_ok) { emit signal_do_login(); hide(); } } [/code]

If I understand you correctly, you have a Fortran program that uses nurses to get user input, and you basically want to convert it to use Qt, but without requiring major modifications to the original code, basically just trying to use Qt as a drop-in replacement. The problem is, Qt (and really all modern GUI packages) operate on a fundamentally different paradigm from ncurses, as you just discovered when you entered the event loop. nurses doesn't have en event loop, you manually step through each screen and your code basically draws them in sequence. Qt is an event-driven architecture: this allows it to respond to mouse clicks, lets you drag windows around, have multiple dialogs up at once, etc.: it's the foundation of modern user interface design. As such, converting from nurses to Qt is not at all straightforward. That is not to say it cannot be done, of course, but you need to reverse the problem: think of the Qt program as your main program, and your Fortran code as running inside of it. You want your various function calls from Fortran to act as events in Qt's event loop, and then write handlers that show the appropriate dialogs and then return the data to the Fortran code. All told, this is a big undertaking: is there a version of this Fortran code that simply reads an input deck (i.e. that doesn't use the nurses stuff)? The way I usually write this sort of interface is to design a GUI that ultimately just writes the input deck out and then triggers the Fortran code to read it.