Comments by califax2k (Top 2 by date)

califax2k 13-May-14 16:41pm View

Well, there are not so many options: there's a DLL. It contains a C-function named engOpen() and it delivers an engine handle. I wrote a C++ class (in my own DLL) and in that class I call engOpen() - easy. No Problem.

I wrote even another class - this time C++/CLI which wraps the first one (because I ultimately I want to pass Information from a C# program (that uses the C++/CLI class) down to the MATLAB engine (that's been created using engOpen()) - but this is not part of the problem.

So, if you ask me, if I'm using the stuff correctly, I'd say yes: because everything links fine - and it even works. DESPITE this one tiny piece that during the engOpen() call (which takes no parameters at all) the Server is to busy dialog opens up. And this happens because a COM object (representing the MATLAB engine) is created.

I my question is: how can I prevent this dialog from appearing....that's all.

califax2k 13-May-14 14:16pm View

Well, what I want to achieve is to instantiate the MATLAB engine and pass some strings down so that it evaluates them. But I don't want to see the "Server is too busy" dialog because this should all happen "in the background".