The @nofilenamequoting seems to be optional, at least in the cases I've tested, but I'd rather be explicit about it, especially here when we're doing something delicate with escaped characters.
Adding noterm means the path won't have any backslash(es) on the end, allowing us to add the exact number we need explicitly.
The "add filename on to path" functionality doesn't know about the escbackslash (since it's outside of the {dlgfolder|...} it applies to), I would not rely on it to correctly preserve the double backslashes at the end of the escaped string when adding a component to the end of the path. We might change it so that does work in both these cases (depending on what's going on behind the scenes), but I like doing it explicitly and not relying on that at all. One less thing to worry about!
@Leo is it accurate to say that External control codesonly apply to that captured/defined by the curly brackets? @Ixp seemed to confirm that in the discussion referenced above but he went on to say to look "further down for an exception". It seems to me that exception is in fact the bug discussed here. @Ixp if you see this maybe you might clarify?
Any comments appreciated as always..