- Joined
- Sep 21, 2017
- Messages
- 462
- Solutions
- 1
- Reaction score
- 237
- Points
- 55
- Favorite Pinball Machine
- Indiana Jones (Williams)
Currently in FP you can use the LogDebugTextToDisk which is great when using AddDebugText. Unfortunately, AddDebugText has a limit in the number of characters wide it will show (63 characters) and this limit is also added to LogDebugTextToDisk() This makes it hard since AddDebugText support a full string.
Can Bam support either:
thanks!
@ravarcade for FYI
EDIT: I know I could always CreateObject("Scripting.FileSystemObject") but that involves\requires different BAM/FP security settings that I don't want to get into.
Can Bam support either:
1. Calling a new xBam.LogAllDebugTextToDisk() which honors the full string passed into AddDebugText?
OR2. Have new xBam.AddDebugText and xBam.LogDebugTextToDisk() which creates a log file in the format of fpTableName.log?
thanks!
@ravarcade for FYI
EDIT: I know I could always CreateObject("Scripting.FileSystemObject") but that involves\requires different BAM/FP security settings that I don't want to get into.
Last edited: