I'd say Qt for sure. Probably the most developed GUI framework out there.Still I am not sure, which GUI to use. It just need to run on Windows. But MFC seems outdated and the C# might just be useful for visualization but not interaction (probably). Any idea which GUI to use to have long term possibility with OpenCascade ?
If the desktop and Windows are the targets, then I would say there are 2 vendors of GUI framework (exclude imgui as it's not the GUI framework but UI library as far as I know) - Windows and Qt.Still I am not sure, which GUI to use. It just need to run on Windows. But MFC seems outdated and the C# might just be useful for visualization but not interaction (probably). Any idea which GUI to use to have long term possibility with OpenCascade ?
I suppose the samples basing on WPF are a good point to start even you're going to deal with UWP apps, at least the integration of OpenCascade graphical services should be more or less the same. Take a look at CSharp samples inside OpenCascade installation package.Hallo JSlyadne,
Thank you for the very thoroughful explanations and recommendations. UWP sounds good, as it were in C++ like OpenCascade. But I never saw a sample coming along with OpenCascade for it, so I wonder if were a development involved in using OpenCascade with UWP GUI. If there is any sample that you are aware of, please provide it.
So far I came to the conclusion to use MFC as I am not sure if the C# OCCTProxy.dll wrapper is useful for visualization or also for interactive features.
@Quaoar: I am close to giving up. I installed OpenCascade 7.6.0 on a new Windows 11 machine. I have installed VS 2022, CMake 3.23 and then I tried from QT 6 down to QT4 all but without success.
Last one I tried was QT 5.12.5. getting fault from CMake:
CMake Error at adm/cmake/occt_toolkit.cmake:35 (include_directories):
include_directories given empty-string as include directory.
Call Stack (most recent call first):
CMake Error at adm/cmake/qt_macro.cmake:48 (qt4_wrap_cpp):
Unknown CMake command "qt4_wrap_cpp".
Call Stack (most recent call first):
What is a working combination within OCC with QT? Is Windows 11 not useful ? Shall it be another Visual Studio version or has it to be another compiler though ? Or which QT version shall I try ?
Shall I step down to OCCT 7.4.0 and maybe stepping down to QT 4.8.6 ? with another compiler ?
Hallo JSlyadne,First of all, no panic, not stress! Keep trying - no reason to give up, what you're trying to do is possible
Apart of motivation... If look inside the "qt.cmake" configuration file (aimed to set up the Qt environment) of OpenCascade, we see this -
View attachment 174
what makes me think that Qt5 was not found, and so, the procedure felt down to the "qt4_wrap_cpp()" method, and since Qt4 is not installed, you got the message saying this.
So, at this point you need first to understand why Qt5 isn't found. OpenCascade expects you to point the 3RDPARTY_QT_DIR variable to .../Qt/6.2.3/msvc2019_64/bin. Do that and then make sure that 3RDPARTY_QT_DIR still points where you set - it's a mark that everything is in the order.
The configuration you mentioned, namely OCCT 7.6.0 in combination with Qt5.12.5, is definitely a working combination. Post more information about the failures you face.Regarding Qt4 this is true, but I tried all variants. Regarding the Qt examples I understand your point and will try it.
Most probably an experienced user has no problem to adapt the "minor" issues.
What I miss is a recommended set of software versions that are proven to work without any issue. E.g. VS2022, Version 17.1 + OCCT 7.6.0 + Qt5.12.5. and 3rd parties libraries:.... and so forth. Quaoar did show in one of his tutorials a working system, that is why I used Qt 4.8.2 version but obviously, there is setup work to do if you deviate from this proven path. These minor changes are difficult for me now as I am on the learning path of OCCT and now additionally QT.
thank you for the encouraging message. No, I never give up. Although I am quite sure, I had the set-up as you request, I will evidently try it accordingly. I will keep you updated and if I find a working mode, I will post it.
Then I got the error:
Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22000.
The C compiler identification is MSVC 19.31.31104.0
The CXX compiler identification is MSVC 19.31.31104.0
Detecting C compiler ABI info
Detecting C compiler ABI info - failed
Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.31.31103/bin/Hostx64/x64/cl.exe
Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.31.31103/bin/Hostx64/x64/cl.exe - broken
CMake Error at C:/Program Files/CMake/share/cmake-3.23/Modules/CMakeTestCCompiler.cmake:69 (message):