Every client delivers their workspace with built-in preference seeds and preference variables.
I am OK with the idea that each client workspace might need its own UPF file. Nothing really new there. I do wonder, however, if we have to have different function key menus, docking XMLs and such. I would prefer for my MicroStation to "look" about the same, no matter what workspace I am in, unless there's a REALLY good reason for the difference.
Is there any reason I would HAVE to keep those user preference type files differentiated? Can I use the same non-upf preference files between workspaces?
No problem sharing those other preferences across WorkSpaces from my experience. Just don't try to use your MicroStation preferences in ORD, or vice versa.
I see pros and cons to both keeping them separated by WorkSpace, or using the same for all.
Rod WingSenior Systems Analyst
Answer Verified By: MaryB
Yes, I would be separating things by ENGINENAME (or whatever that variable is) because that DOES make a difference.
I can see some pros for separating by workspace, in case the clients have some special, important setting...but so far I see very little that would require that. Consistency across projects seems like a more important factor for us.
Thank you.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Hi Mary,
I think you could redefine _USTN_PREFNAMEBASE in a WorkSpace CFG to include the WorkSpace name:
_USTN_PREFNAMEBASE = $(_USTN_HOMEPREFS)$(_USTN_USERNAME)-$(_ENGINENAME)-$(USTN_WORKSPACENAME)
But haven't tried that combination.
Marc