I still get support requests for a bug in DoScript that seems to be related to Leopard.
I did a simple test with an example file included with the plug-in ( example 6 ):
I set the formula to this:
Let (
[
$$windowName = Get ( WindowName ) ;
$$alarmTime = example 6::alarm time ;
$$recordNumber = Get ( RecordNumber ) ;
$$occurrence = Get ( LayoutTableName ) ;
$$currentTime = Get ( CurrentTime ) ;
$$notes = example 6::notes & "x"
] ;
if ( Get ( CurrentTime ) ≥ example 6::alarm time ; mFMb_DoScript( "[event] Timer" ) ; False
)
)
Everything is set, except that this formula, which is evaluated from the plug-in, is not able
to resolve the fields, it simply returns nothing for them.
The same plug-in compiled for Windows works OK. The same plug-in in Tiger works OK.
This erratic behaviour is present since the first version of Leopard, and after 1 year, I still
see the same error.
Am I doing something wrong in my code, or is FileMaker forgetting to fix some
compatibility bugs?
In a nutshell, this is what I'm doing:
fmx::ExprEnvAutoPtr expressionEnvironment ;
FMX_SetToCurrentEnv( expressionEnvironment.get() ) ;
fmx::DataAutoPtr alarmResult;
expressionEnvironment->Evaluate( *alarmInstruction, *alarmResult );
It seem to me like FileMaker running in Leopard is having problems with the
expressionEnvironment, not being able to get the contents of fields.
