mcgui tests and more

[Kristian Nielsen]

> Date: Wed, 23 Feb 2000 09:33:12 +0100
> From: Farhi <farhi at ill.fr>

> I've tested the two versions
> 1- mcgui-1.pl : crash, here if the trace output
> 2- mcgui-2.pl : cannot fork

Ok, thanks for the information. It seems pretty clear that the problem
is that when another program is called (whether the mcstas compiler or a
simple echo), it causes a conflict with the Tk/X connection. The "cannot
fork" is just the Perl debugger; could you should try mcgui-2.pl without
the debugger and see if it crashes? If possible, we should also try with
a newer version of Perl, though that will probably mean a lot of work
for Ron. I will think some more about the problem and maybe ask on the
Perl/Tk mailing list.

> I'm now finisshing a general Monitor component. It can handle any kind
> of output (0D, 1D and 2D, and multiple 1D output), with 'intelligent'
> features when they are not provided by user. This should avoid people
> from writing dozens of monitors on the same model. I tell you when I

Sounds very good! A solution to the  "dozens of monitors" problem would
be very nice indeed!

> incorporate it to the unofficial components and automatic web page. This
> latter works ok, but can you also sort components by category in the
> list ?

In fact, I already did :-)

    http://neutron.risoe.dk/mcstas/mcdoc/test/

My development version of McStas also uses subdirectories for components
as you suggested. I also have default values for component parameters
and instrument parameters that have string values.

 - Kristian.