[argyllcms] Re: Executing dispread from Mono
- From: Pascal de Bruijn <pmjdebruijn@xxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Sun, 19 Apr 2009 14:54:58 +0200
On Wed, Apr 15, 2009 at 6:55 PM, Pascal de Bruijn <pmjdebruijn@xxxxxxxxx> wrote:
> Hi,
>
> I'm trying to write a very simple wrapper for dispread using
> Mono/Gtk#, thus far I haven't
> written anything serious, but I'm just experimenting.
>
> However, dispread seems to fail when I start it from Mono...
>
> Number of patches = 288
> Setting up the instrument
>
> When using the debugging feature, I get this output:
>
> huey: About to init coms
> huey: About to init USB
> icoms: About to set usb port characteristics
> icoms: About to open the USB port
> icoms: USB port needs opening
> icoms: About to open USB port 'usb:/bus0/dev6 (GretagMacbeth Huey)'
> icoms: USB port is now open
> icoms: Clearing any USB errors
> icoms: usb port characteristics set ok
> huey: Sending cmd 'GetStatus' args '01 00 00 00 00 00 00'icoms:
> About to do control 21, 09 0200 0000 0008
> icoms: Writing control data 00 01 00 00 00 00 00 00
>
> Whenever I use dispread normally, from a commandline, I see the Huey
> lights blink
> before calibration starts, that never happens here. Also the patch
> reading area in the
> center of the screen is never drawn.
>
> I'm not blaming dispread, possibly Mono prevents dispread from doing something
> properly. However, I'm not sure where to start looking.
>
> Could you possibly provide me with some hints as to where possible problems
> may lie?
When I execute:
dispread -D 1 -v -y l test < in
With the file 'in' only containing a newline, dispread (1.0.3) segfaults...
Is this expected behaviour?
Regards,
Pascal de Bruijn
Other related posts: