Engauge Digitizer

This is most likely no longer a problem with an up to date operating
system, compiler and engauge release. Please comment otherwise.

Logged In: YES
user_id=654662

Just noticed that SynapseDict compiles even though it is set up in
almost the same way. The difference is that SynapseDict is in the
public section, so my first guess is probably correct. Moving the
NeuronDict typedef to the public section will fix that problem.

Logged In: YES
user_id=654662

The first problem is that the typedef NeuronDict is not available to
the Neuron class. My guess is that although both the NeuronDict
and Neuron are helper classes for the same GridRemoval class,
that the NeuronDict typedef must be moved up to the public
section. Otherwise, there is a small chance that just replacing
'NeuronDict' by 'GridRemoval::NeuronDict' inside Neuron, will fix the
problem. Otherwise, maybe using 'friend' will fix it.

Forte seems to be quite inflexible with its casting. A few minutes
of research came up with the idea of turning off the
SCM_DEBUG_TYPING_STRICTNESS flag, to remove the DigitDoc
errors. If the line you are having problems with is 'str<<(const
Q_INT32&)MagicNumber;', then you might try removing the 'const'
and '&'.

I have compiled Engauge on a Solaris box with g++, which is one
of the Sourceforge compile farm servers. However, I cannot test
it since X tunneling is turned off.

If I had a Forte compiler I could give you a better response.

Good luck
-Mark Mitchell