Tie opencv, Qt and Vimba together in a C++ APP. improve buildsystem from subl. Add logging.

b @ 44f1b32f

-Subproject commit e46499390986da1f889f78c0110e385003791dc6
+Subproject commit 44f1b32f01c0112b25a655b50dffe5b91226794d

dox/notes_C

@@ -230,3 +230,8 @@ apt install libarchive-dev python3-pybind11
 #else
   frame = new IplImage(img_input);
 #endif
+
+
+###############################
+Q: can i use OPENCV for BGS?
+	hint: -lopencv_bgsegm ??? can i use it for SW_C ?

dox/scrap

+SCRAP
+######
+void AsynchronousOpenCVRecorder::Log( std::string strMsg, VmbErrorType eErr )
+{
+		strMsg += "..." + m_ApiController.ErrorCodeToMessage( eErr );
+		ui.m_ListLog->insertItem( 0, QString::fromStdString( strMsg ) );
+}
+
+QObject::connectSlotsByName() ?? :)
+
+

dox/todo_tron

@@ -19,11 +19,14 @@ B) recorder
 ============================
 	> print Info: Versions (VimbaApi, OpenCV, Qt)
 					more: cams
+	> wait and detect cams
+	> produce frames & timestamps
+	> build GUI
+		--> Q: might a console app be feasable??
+============================
 	> central config
 		> threads for started recordings [PID]
 		> storage folder
-	> wait and detect cams
-	> produce frames & timestamps
 
 	> export settings with viewer
 	> load settings with sw