 | | | Setting Custom Environment Variables | Setting Custom Environment Variables 2005-06-17 - By kim aldis
Back
You're talking about different paths for different machines?
There's a couple of methods come to mind.
Set environment variables within the setenv.bat - or set the setenv.bat to
call a .bat of your own, which is better. The way I do this is have my own
single starter .bat file which every machine uses to start xsi. This calls
setenv.bat then my custom, local .bat, then xsi.
Use a plugin, which loads automatically. Have it in your workgroup but have
it open and parse a local file. Use a command in the plugin to parse the
file and return your value.
Again, use a plugin but have a hash table in the plugin that stores
machine/value pairs.
Set system wide environment variable and use the windows scripting object to
retrieve their values.
Of all of these I prefer the hash table method. It keeps everything in one
place for easy maintenance.
> -- --Original Message-- --
> From: owner-xsi@(protected)
> [mailto:owner-xsi@(protected)] On Behalf Of Matthias Worch
> Sent: 16 June 2005 22:30
> To: Andrew Skowronski
> Cc: XSI@(protected)
> Subject: Re: Setting Custom Environment Variables
>
> Unfortunately I can't remap drives on my work machine without
> a whole lot of trouble, so storing a string with the pathname
> would be the cleanest solution.
>
> XSI does have the concept of an %appdir (or something
> similar, can't find any documentation right now), right?
> Could that be extended?
>
> --
> Matthias Worch
> http://www.langsuyar.com
>
> AS> A very simple approach would be to use a subst drive, e.g. "Y:".
> AS> Each machine might have a different definition of where
> Y: is, but
> AS> if you always refer to it as Y: from within XSI, it could work.
>
> AS> -Andrew
>
> AS> -- --Original Message-- --
> AS> From: owner-xsi@(protected)
> AS> [mailto:owner-xsi@(protected)]On Behalf Of Matthias
> Worch Posted
> AS> At: Thursday, June 16, 2005 2:15 PM Posted To: xsi
> AS> Conversation: Setting Custom Environment Variables
> AS> Subject: Setting Custom Environment Variables
>
>
> AS> At least that's what I think I want. I'm looking for a
> way to set a
> AS> variable that stores part of a system path. I frequently transfer
> AS> data between computers, and various assets (such as my custom
> AS> noIcon.pic) are saved in different locations and can't be
> resolved
> AS> on one computer or the other.
> AS> I'd like to create a variable that can be part of the
> pathname. So
> AS> assign $NOICON to c:\foo and then set the path inside XSI to
> AS> $NOICON\rsrc\noIcon.pic. Obviously $NOICON would point to a
> AS> different directory on other computers.
>
> AS> Is this possible? I could imagine writing a script that resolves
> AS> pathnames of a scene when it is opened, but is there an
> easier way?
> AS> I dug through the "data management" section of the
> reference docs,
> AS> but nothing there seems to provide me what I need. My
> computers are
> AS> not part of the same network, so AFAIK workgroups
> don't...well, work.
>
> AS> --
> AS> Matthias Worch
> AS> http://www.langsuyar.com
>
> AS> ---
> AS> Unsubscribe? Mail Majordomo@(protected) with the
> following text in body:
> AS> unsubscribe xsi
>
> AS> ---
> AS> Unsubscribe? Mail Majordomo@(protected) with the
> following text in body:
> AS> unsubscribe xsi
>
>
> ---
> Unsubscribe? Mail Majordomo@(protected) with the following
> text in body:
> unsubscribe xsi
>
>
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
|
|
|