Hello Johnnie,
Is the worker function (in the worker class) running on a separate
thread? Is it started using a Thread/ThreadPool/BeginInvoke? This is
probably the case, but it's not clear from the code you've provided. Can
you show the code that calls radiazerMain? Main.cs?
Normally, only o
Hello,
I use the serial port class a lot, but always through the synchronous
Read and Write methods. This works great.
Looking at the mono source code for the SerialPort class, the events
seem to exist, but are not called from anywhere, so they are probably
not yet implemented (as is stated
Hi Gelin,
I think mono is doing a good job, especially for backend uses. LISTEQ
uses it to host their BoXedVDI Cloud Desktop software (www.listeq.com) -
where the mono/.net application handles all the network I/O, video
compression and encryption. I also use mono for much of the
globaltuners.
While working on an interface between VirtualBox and C# on Linux, I ran
into a problem, which I think may be a bug in the mono code.
The System.Runtime.InteropServices.Marshal.GetObjectForIUnknown function
releases (using Marshal.Release) the given COM pointer. Microsoft's
documentation does no
In Mono COM/XPCOM interop, Runtime Callable Wrappers appear to be
implemented and work correctly with VirtualBox, although it's not
directly compatible with COM interop in the Microsoft .Net runtime: the
interop assemblies generated by VS.Net cause crashes (segmentation
fault) and for interface
ons.
The InterfaceType attribute is interesting. I believe interfaces are
dual by default (IDispatch based with a vtable), so if your interfaces
really are dual this should work.
Thanks,
Jonathan
On Tue, Apr 26, 2011 at 4:47 PM, Ivo Smits <mailto:i...@ufo-net.nl>> wrote:
In Mon
Jonathan (and others),
I don't think this issue is playing up yet at run time. None of the
complex/bigger COM objects are released yet, until the application
finishes. At that point I sometimes receive a SIGSEGV, which may be
caused by the releasing of the COM objects. It's no big deal yet. As
Wikipedia described how this can be done:
http://en.wikipedia.org/wiki/Dynamic_loading#In_C.2FC.2B.2B
It's not so difficult at all. You just need to create function pointer
variables for the functions you want to call, then use dlopen(...) to
open the mono library, and dlsym(...) to lookup a sy
Op 20-7-2011 15:14, Tom Spink schreef:
> Hi Guys - if you're still watching this thread,
>
> So I may have done something brilliant - or something terrible. I
> don't quite know yet - I need your feedback to see if I'm heading
> along the right lines.
>
> What I've done is to create a tool that
Op 22-7-2011 17:05, Andy Hume schreef:
> That was the most beautiful ugly thing I've seen in a long time. :-)
> Unfortunately I haven't managed to get it to work:
> 1) Try [DllImport("__Internal")] extern int _wapi_socket(..)
> Swallowed Exception: System.EntryPointNotFoundException: _wapi_socket
>
Op 21-9-2011 8:31, noisecrime schreef:
> ...
>
> Essentially the function has three nested loops, all of which iterate the
> same number of times every call. The inner loop is a single line of simple
> arithmetic instructions akin to x[i] = y[i] + (a * ( y[s] + y[t] + y[u] +
> y[v]) )/c. It normal
11 matches
Mail list logo
