Plotter Driver Variables Explanation Needed

Worth a read:

 http://communities.bentley.com/Communities/Other_Communities/AskInga/w/AskInga/viewing-and-determining-the-configuration-variables-.aspx

Bear:

 http://communities.bentley.com/Communities/Other_Communities/AskInga/w/AskInga/viewing-and-determining-the-configuration-variables-.aspx

Bear, thank you. The debug option alone in that is awesome! Thanks man.

Phil Chouinard:

For the second question, it is unclear if you are looking to change the filename as opposed to using the exact filename. For the latter, you might want to take a look at using:

"$(basename(_DGNFILE)).LRG"


for your default_outFile... statement in the PLT file you are using.

I'm trying to turn a file named 123bdr.dgn into 00123sd.lrg (for Stormwater) or 45bdr.dgn into 00045wa.lrg. The Border Pages ("bdr") are unique (don't ask me why) in that they don't have the padding of zeroes that are needed for the lrg file. So page 19 for Border Pages is just "19bdr.dgn" whereas when I print the Stormwater view of that same border page I have to add padding zeroes up to 5 digits to make it "00019sd.lrg" I don't think it can be done like I want it to with just variables, but I have hope! The other option is to remove the extension, the dot, and three characters all from the rightside of the filename + extension and replace with the 2 character discipline + .lrg and then deal without the padding zeroes. It's not a HUGE time saver, but if the guys could just double click the StormwaterLRG.plt file and forget about dealing with which folder it had to go into? I think they would REALLY dig it.

Phil Chouinard:

BTW, it might be better to post one inquiry per thread... we have found that makes it easier to follow (and find) specific topics.

Good point. I'll do that in the future. I just came here with 30 questions running through my head and didn't wanna lose any of them.

WRT the print file name part, there are some things you can do with configuration variables, but that is somewhat limited. There is a section in Help > Contents that might be worth a looksee... search for "Variable definition references" for what is possible to extract and "build" definitions. From what you further describe, you might be looking at a VBA macro to achieve what you are after.

Not really sure about the "...could just double click the StormwaterLRG.plt file and forget about dealing with which folder it had to go into" part... is that another topic? FWIW, you can put print output in any place you want -- either let MicroStation do that for you (through a configuration variable) or in the same folder as the DGN file you are in or some other place that you desire. That said, if that is what you want to do, you might want to start a new topic on that :)

WRT the print file name part, there are some things you can do with configuration variables, but that is somewhat limited. There is a section in Help > Contents that might be worth a looksee... search for "Variable definition references" for what is possible to extract and "build" definitions. From what you further describe, you might be looking at a VBA macro to achieve what you are after.

Not really sure about the "...could just double click the StormwaterLRG.plt file and forget about dealing with which folder it had to go into" part... is that another topic? FWIW, you can put print output in any place you want -- either let MicroStation do that for you (through a configuration variable) or in the same folder as the DGN file you are in or some other place that you desire. That said, if that is what you want to do, you might want to start a new topic on that :)