I figured it out before you sent your email. I'm not sure where you got the
"+" from, but that isn't a valid Codewright command line parameter (at least
not in any of the versions I have used).

 I don't think there is anything you need to report to the IDE guys (maybe
remind the help file person to add the parameters and to remove the
reference that this is a Mac only feature)

For anyone interested, to get Codewright to work as an external editor, use
the following:

Launch Editor:               D:\path\cw32.exe %file
Launch Editor w/Line #: D:\path\cw32.exe %file -G%line

You can also add the -S- to suppress the state file if you want, and
the -NOSPLASH to kill the splash screen.

-----Original Message-----
From: Jun-Kiat Lam [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 31, 1999 1:25 PM
To: [EMAIL PROTECTED]
Subject: Re: CodeWarrior Patch Released


It's supposed to be (again exact command):

c:\program files\codewright\cw32.exe +%line %file

but it looks like it isn't working properly. Right now I'd stick with the
original

c:\program files\codewright\cw32.exe %file

in the 'Launch Editor w/ Line#' box.

the original idea was that with the first setting you could click on a
warning or error and have it open the file externally at the line#. I'll log
this with the IDE guys.

JK Lam
Metrowerks Technical Support

----- Original Message -----
From: Bryan Nystrom <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 31, 1999 12:27 PM
Subject: RE: CodeWarrior Patch Released


> Thanks.
>
> What about the "line number", or is it %line?
>
> -----Original Message-----
> From: Jun-Kiat Lam [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 31, 1999 9:35 AM
> To: [EMAIL PROTECTED]
> Subject: Re: CodeWarrior Patch Released
>
>
> Hi Bryan,
>
> To use the external editor feature, use this exact command in 'Launch w/
> Editor' box
>
> c:\program files\codewright\cw32.exe %file
>
> This should open up the CodeWright editor when you double click on main.c.
> If you select New from the File menu though, it will still create a new
file
> in CW editor, not the CodeWright editor.
>
> Hope this helps.
>
> Rgds,
> JK Lam
> Metrowerks Technical Support
>
> ----- Original Message -----
> From: Bryan Nystrom <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, March 30, 1999 4:47 PM
> Subject: RE: CodeWarrior Patch Released
>
>
> > One of the few "undocumented" features that they have included in this
> patch
> > is the ability to launch an external editor (windows). The only problem
is
> > that the feature is "too" undocumented. Could anyone from MW please give
> us
> > some help on how to configure the command line for passing the file name
> and
> > line number?
> >
> > So, if my editor is CodeWright, and I need to pass "CW32.exe main.c" to
> the
> > command line, what do I use to substitute the "main.c" in the preference
> > window?
> >
> > This is a welcome feature, if it works! Thanks.
> >
> > -----Original Message-----
> > From: Chris Antos [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, March 30, 1999 4:13 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: CodeWarrior Patch Released
> >
> >
> > fyi, the only real problem that the patch fixes is the PalmRez crash.
> > (which is affecting everyone who uses Constructor for the resources, but
> not
> > me b/c i still use PilRC and the standalone RCPalm post-linker).  the
> black
> > bitmaps and the other commonly reported bugs are not fixed yet.
> >
> >
> > -----Original Message-----
> > From: Andrew Ball <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> > Date: Tuesday, March 30, 1999 6:56 AM
> > Subject: CodeWarrior Patch Released
> >
> >
> > >I was prowling around the Metrowerks site last night and noticed that
the
> > >patch for R5 has been released.
> > >
> > >Special note in the README:
> > >
> > >Apparently, this patch is not for use with "merged" installations
(where
> R4
> > >and PalmOS R5 were merged into one).
> > >
> > >You can download the patch from:
> > >
> > >http://www.metrowerks.com/products.q?p=CWPP&v=5&x=updates
> >
> >
> >
> >
> >
>
>
>
>



Reply via email to