Back to Documentation

FAQ 2

my breakpoints do not work…

I couldn't live myself without the debugger, so yes they do work.

BUT!

to get into the debugger you must of course add the table script to your (or better a seperate) castlib. I bet you figured that out yourself already.

another BUT!

there is still another requirement: in order to work from the LDM, in protected mode, all scripts are grabbed from the LDM at the beginning and stored in a "global" list. so the user can even remove the castlib or the LDM and the scripts are fed from memory (-> from that "global" list). These are the scripts (templates for the instances) and not scriptinstances.

Now as soon as I need one of these scripts, I get the script (-template / -prototype) with mGetXScript(#nameOfScript) (or the shorter wrapper xscr()) and then make an instance out of the script.

It is just like a castlib with scripts stored in a list in memory. That way one can store compiled scripts in memory, without a hassle, when all scripts are recompiled and the scripttext for the protected scripts is missing. (what would be the case, if you just linked a cxt with protected scripts -> on every recompile director would complain)

Now, if you put the "DrawTableParent" script into your castlib, but still have "aleXtraLoader" loading the LDM, the script from the LDM will be used instead of the one in your castlib. Either you prevent "aleXtraLoader" from loading the LDM (with the risk of other scripts from the LDM missing) or you "overwrite" certain "script templates" only. In order to do so, just load the scripts you want to debug AFTER the LDM scripts were loaded.

I usually do it like so:

• make a new castlib "alextras"
• put the scripts I want to override into that castlib (DO NOT RENAME THEM, the name DOES matter!)
• open the behavior "aleXtraLoader" go to line 104 and add the follwoing line:

mLoadScripts "alextras"

since I didn't provide the source for these movies, there was never a need to document that, as this used to be for myself only.