11-13-2008 07:14 AM
Hi,ACiDuser,
>Sorry for offtopic, but I follow this hard discussion with high interest... Its just interesting for me - what occurred first - you will get stuff running, or you will change the architecture a little bit for avoid such interconnection between >LabVIEW and console...
Please don't hesitate to post here final solution when you will get it. Thanks.
Andrey.
Hi!
I'm trying to implement now a solution LabView + DLL (opening console via AllocConsole) cause it requires very small amount of code - to be edited.
Previous, when I got those debug messages passing directly to LabView with Array of Strings, I received error on a final step - and a system reboot.
At first it was an .exe application. It works now - just fine. Then I recompiled it as a DLL and also added an exported function for labview.
I'm not an expert in system/driver programming - so it is quite hard to determine errors causes. So I try different possible solutions to get this hell driver to work 🙂
Regards
11-20-2008 11:00 AM
Hello!
This peace of code:
AllocConsole();
freopen("CONOUT$","a+",stdout);
freopen("CONIN$","a+",stdin);
Allocates new console, and redirects standard output and input. So I don't need to change whole project code and I am able to see printf outputs
and use keyboard inputs.
But I steel must wait until the Console window finishes it's execution and only then I can use LabView front panel.
It is a great disadvantage.
Trying OpenG to use keyboard inputs - did not bring any result.