In an Export plug-in, I need to read in the destination file path from scripting parameters. Often, the character at exportPath is junk and not an actual part of the path (hence the check). Recently, this junk has actually been alphanumeric characters. I can write a more accurate platform-dependent workaround, but would prefer an actual solution. As a note, this happens whenever I use PIGetStr, not just in the case of reading filepaths.
Is there a standard way to handle this behavior?
byte offset = 0;
offset = 1;
strcpy_s((char*)gDestination, 256 - offset, (char*)exportPath + offset);
DescParams->playInfo = 0; //Don't pop dialog.
Result in exportPath: Ec:\temp\assets\textures\brick_stacked_tile_01_SpecColor_gradients.dd s
So, those things that show up in green tell you how to use someone elses programming constructs. Fascinating stuff.
/facepalm. I even went to the definition in PITypes.h, and looked at it and was like "Hey, it's an unsigned character array of 256 characters" and never read the comment next to it.
Thank you for answering my question. It seems like I need to pay more attention to details in the future.