ddobrev
commented
8 years ago Thank you for the effort to create those samples, they are definitely going to help progress.
- As soon as I am able to, I am going to check loading *.ui-s and fix the errors;
- We do not handle char\ as well as we could in C++#, it's a missing feature. One of my end goals is definitely to remove any pointers from the generated API. It just needs more work to cover all cases. Before this summer it was even worse but thanks to @genuinelucifer we now have ref parameters instead of pointers;
- QApplication.Exec() is there, it's just static. The pattern to use in Qt is QApplication app(argc, argv); ... return QApplication::exec();
- I am afraid it won't help because I already use the latest C++#. It needs debugging.
I will get back to you when I have more time. Then we might think about merging your samples into the Qt# repo.
Hecatron
Hi,
I've recently created a couple of test apps over here https://github.com/grbd/QtSharp.TestApps just to see if I could create a basic form, or load in a ui file. As you've mentioned I've stuck with VS2013 and avoided VS2015, and so far I've been using the the CppSharp dll's from the QtSharp repo (Also the apps are already set to x86)
It looks as if some functions work, but others generate AccessViolationException errors. Showing a form or loading a ui file seems to be out of the question for the moment
One thing I did notice is in relation to the QApplication class, for argv it seems to take a char\ parameter which I think means it's unmanaged / unwrapped. I was able to get around this with some marsheling in C# although this rules out the use of VB for now, and it means you have to use unsafe code blocks. Also it looks like QApplication is missing the exec function, which is one of the core ones needed to run a QT App.
I realise these are probably Cppsharp related problems, but I just thought to mention them for info. The last thing I'm going to try is rebuilding the latest CppSharp to see if that makes any difference.