🚀 go-pugleaf

In article <BAD067F4.29F2D%scott_ribe@killerbytes.com>,
 Scott Ribe <scott_ribe@killerbytes.com> wrote:

> in article 73a6cacd.0304261207.1d910740@posting.google.com, kraka at
> elin@acm.org wrote on 04/26/2003 2:07 PM:
> 
> > Please help me with a work around and preferably also an explanation
> > as to what is going on
> 
> You don't happen to have another project running which uses that file do
> you? I'm working on a client/server app, and I notice that if I have the
> server running under the debugger, am working on the client (a common
> situation for me), and try to edit a file that is common to both projects, I
> get that error until I kill the server process.
> 

Also.  Debug a client app running on a test machine by connecting to 
your dev machine and double clicking on the .sym file (that way I'm 
always running the most recent version).  Now do something that crashes 
(test machine's) Codewarrior or crash the test machine.  Now CW on my 
dev machine thinks any file that I had open on my test machine is still 
open, therefore locked.  I can get around that by dragging the file into 
Project Builder and saving the file after a non-change 
(space-delete-save).  Now CW is happy again.  Relaunching CW would 
probably work but I don't have that kind of time :-)

H.

-- 
To reply via email, replace "LastNameHere" with my last name.