Thanks Tom and Lars-Olof for your comments.
I've found the cause why the DLL wasn't working.
The triggers code field was set to DLL and the DLL template code was correctly inserted. But then I've used the button left of the code button (no idea what the buttons name is but it shows an icon with a paper and lines on it and is between erase button and code button, maybe template button?) to edit the DLL's name and function's name. Then I clicked OK and the error persisted. When I checked the code of the trigger again its type was reset to Flexscript instead of DLL. So i played with it a bit and found that the code fields type is reset when the template window (i call it that way) is opened in ordner to change the DLL's name and function. In case the code field is used to change the DLL's name and function without opening the template window everything works perfectly well.
In addition the code type's locked checkbox does not make eny difference if checked or not.
Maybe somebody else can confirm that behavior as I would assume the template window should be used to change the DLL's name instead of the code field after its type has been set to DLL.
I'm not sure if this behaviour is intented or if this is a bug. Anyway, my DLL is now working as long as I do not touch the template window.
Cheers,
Stephan
__________________
---
You can't have it both ways.
|
