CodeManager Force_Dir Force_Prj vars
Charles Wilson
In article <326E59...@diehlgraphsoft.com>, Jeffrey Koppi
<jko...@diehlgraphsoft.com> wrote:
> I am confused about the use of the Force_Dir and Force_Prj variables.
> I set them both to true and now when I execute the "mwcm cp .."
> command to go up one project, it says it's changing the directory also.
> But if I issue an MPW "directory" command, it says I am still at the
> sub directory.
The CodeManager MPW tool mwcm only changes the directory within the scope
of its execution. This is to say that while it running it may change the
Macintosh's working directory. It does not change MPW current directory as
set by the directory command. With CodeManager 1.0.6 you must, in general,
do an MPW directory command into the directory you wish the files to end
up in. With CodeManager Release 3 ( MPW tools 1.0.7 ) you can have the
change project command ( CP ) emit the command itself. It works as
follows:
mwcm cp '$:gopher:golf ball'
This will usually tell you that the project has changed. If you are not in
the directory which has been associated with that project, you will be
informed that the directory has changed also.
mwcm cp -e '$:gopher:golf ball'
Will perform the same internal actions but will output an MPW executable
command string instead of the usual project/directory announcements. This
may be used to change the MPW working directory by enclosing the entire
command in back ticks as follows:
`mwcm cp -e '$:gopher:golf ball'`
Projector gets around much of the standard MPW tool restrictions as it
isn't an MPW tool at all, it's part of the MPW Shell itself.
- charles
---------------------------------------------------------------
Charles Wilson ////\\\\\///\
Metrowerks Corporation ////\\\\////\\\
2201 Donley Drive / Suite 310 //// //// \\\\
Austin TX 78758-4548 //// //// \\\\
United State of America //// //// \\\\
Jeffrey Koppi
I have a few questions about using CodeManager 1.0.6 with MPW.
I am confused about the use of the Force_Dir and Force_Prj variables.
I set them both to true and now when I execute the "mwcm cp .."
command to go up one project, it says it's changing the directory also.
But if I issue an MPW "directory" command, it says I am still at the
sub directory.
The CodeManager User's Guide does not clearly define the terms
"Current" and "Working" directory. Are they two different things,
and if so which is which?
I want to make sure files get checked out to the correct directory.
With Apple's Projector I simply did a "CheckOutDir" command for each
project and everything worked. What should I be doing with CodeManager/
SourceSafe to ensure this behavior?
----
Following is a clipping from my MPW worksheet:
mwcm cp
Current project is '$/Stimpy/Source'
pwd
DevSource:Projects:Stimpy:Source:
mwcm cp ..
Current project is '$/Stimpy'
Changing directory to 'DevSource:Projects:Stimpy:'
directory
DevSource:Projects:Stimpy:Source:
----
Thanks for your help,
Jeff
--
--------------------------------------------------------------------------------
Jeffrey Koppi Diehl Graphsoft, Inc. 410-290-5114
ext 660
jko...@diehlgraphsoft.com Columbia, MD
www.diehlgraphsoft.com
--------------------------------------------------------------------------------
Jeff Pek
> I have a few questions about using CodeManager 1.0.6 with MPW.
>
> I am confused about the use of the Force_Dir and Force_Prj variables.
> I set them both to true and now when I execute the "mwcm cp .."
> command to go up one project, it says it's changing the directory also.
> But if I issue an MPW "directory" command, it says I am still at the
> sub directory.
>
> The CodeManager User's Guide does not clearly define the terms
> "Current" and "Working" directory. Are they two different things,
> and if so which is which?
>
> I want to make sure files get checked out to the correct directory.
> With Apple's Projector I simply did a "CheckOutDir" command for each
> project and everything worked. What should I be doing with CodeManager/
> SourceSafe to ensure this behavior?
I saw this problem too. It appears that CM will, when you check out or
check in files, use the correct directory, but if you try to add, you'll
have problems. Then, you need to use the directory command to set the
current directory properly.
I saw Charles' response to your question, but I'm not sure I understand'
it! Can you clarify, Charles?
hth - jeff
--
Jeff Pek
Development Manager
Gene Codes Corp - Ann Arbor, MI
jp...@genecodes.com
Charles Wilson
In article <jpek-ya02318000...@cnews.branch.com>,
jp...@bizserve.com (Jeff Pek) wrote:
> In article <326E59...@diehlgraphsoft.com>, Jeffrey Koppi
> <jko...@diehlgraphsoft.com> wrote:
>
> > I am confused about the use of the Force_Dir and Force_Prj variables.
> > I set them both to true and now when I execute the "mwcm cp .."
> > command to go up one project, it says it's changing the directory also.
> > But if I issue an MPW "directory" command, it says I am still at the
> > sub directory.
>
> I saw this problem too. It appears that CM will, when you check out or
> check in files, use the correct directory, but if you try to add, you'll
> have problems. Then, you need to use the directory command to set the
> current directory properly.
>
> I saw Charles' response to your question, but I'm not sure I understand'
> it! Can you clarify, Charles?
Basically, MPW commands can't change the MPW directory. Projector can do
stuff other MPW tools can't because it's not an MPW tool, it's part of the
MPW Shell application. The 1.0.7 version will allow you to have
CodeManager generate a directory command string that you can execute.