On the OpenCS issue I'm having - I don't know what is going on. I've run the debugger again, this time mId is of wchar_t type (I didn't change) and has the correct string, i.e. "d:\\Users\\Dad\\Documents\\My Games\\openmw/data\\Morrowind.omwgame". Don't know why it was different earlier
Unfortunately still crashes at the same spot.
EDIT: more strangeness - when I run a debug version mId is now "Zebabi" which is the cell name.
QtGuid4.dll!QList<QPointer<QWidget> >::QList<QPointer<QWidget> >(const QList<QPointer<QWidget> > & l) Line 122 C++
QtGuid4.dll!QForeachContainer<QList<QPointer<QWidget> > >::QForeachContainer<QList<QPointer<QWidget> > >(const QList<QPointer<QWidget> > & t) Line 2394 C++
QtGuid4.dll!qForeachContainerNew<QList<QPointer<QWidget> > >(const QList<QPointer<QWidget> > & t) Line 2404 C++
QtGuid4.dll!QWidgetPrivate::setParent_sys(QWidget * parent, QFlags<enum Qt::WindowType> f) Line 636 C++
QtGuid4.dll!QWidget::setParent(QWidget * parent, QFlags<enum Qt::WindowType> f) Line 10215 C++
QtGuid4.dll!QWidget::setParent(QWidget * parent) Line 10161 C++
QtGuid4.dll!QLayoutPrivate::reparentChildWidgets(QWidget * mw) Line 981 C++
QtGuid4.dll!QWidget::setLayout(QLayout * l) Line 9831 C++
> opencs.exe!CSVWorld::SceneSubView::SceneSubView(const CSMWorld::UniversalId & id, CSMDoc::Document & document) Line 71 C++
I am sorry, but you are completely on the wrong track. There are no paths involved here. If you see a path there, then something got corrupted (heap maybe?).
Also, this here
EDIT: maybe CSMWorld::UniversalId::mId should be of type std::wstring instead?
EDIT2: that won't be a quick fix solution, as std::string mId is in lots of places. maybe convert into a simple string before creating that class
is a problem. I don't mean to offend, but these statements are terrible. Using std::wstring in a multi platform project is bad. Very bad. Some might argue that using wstring at all is bad (see http://www.utf8everywhere.org/). std::string is the right string type for most cases.
yeah, no doubt I'm on the wrong track and yes, looks like something is being corrupted
also, no offence taken, I tend to babble on without knowing all the facts. If you need to correct me, go ahead and correct me
EDIT: Read that article as well as other opinions on the net, it seems that not everyone agrees on what the "best" way is but I guess almost everything is like that. I have no wish to further that debate here.
The wizard is currently complete enough to be functional, the only thing I need to sort out is how to stop the thread properly when the user cancels the installation process. Right now it just kills the thread which results in valgrind complaining about unreachable memory and stuff. I need to add checks in every labor-intensive task in the thread so it can emit a finished signal and clean up before the process quits.
I just came back from a weeklong stay abroad but I will have some spare time this weekend and next week to work on this. The wizard might be a nice feature for the 0.30.0 release if I manage to get it done in time.
Depends on when the release happens. Still waiting on feedback regarding the icons. If nothing happens there, we can as well enter RC phase at the beginning of next week and I would rather have this new launcher chance in the code base for a while (for the purpose of testing) before we include it in a release.
Any chance for getting 1275 and 1274 into 0.30.0? After feeling better i can see that I need to add just a few additional lines into paged worldspace widget (handling interior cells, changing toolbar, etc.).
PS
actually it is a bit more complicated, as i see.
It seems we have some usable icons now. That still doesn't address the entire problem, but maybe WeirdSexy can demonstrate the function of the remaining mis-labeled buttons in his video.
I know there is still some ongoing work in the AI department. Are we in a state that allows us to enter the RC phase within the next couple of days?
Reporting in. I should be good to handle all of my video-commentary duties at this time. However, I will be traveling for a few weeks starting next week and will not have access to a powerful computer (probably).
