Re: [Codestriker-user] No new browser window opened up after clicked on the line number.
Brought to you by:
sits
|
From: Gary Y. <gar...@ya...> - 2009-05-07 18:29:06
|
David,
I am not talking about the line numbers used to add comments. It works fine. I am talking about the Line number next to the "Parallel".
At the Codestriker Guide, 3.5.3 Viewing Complete old/new Files. It syas:
As mention in Section 3.5.1, it is possible to view the entire contents of a file in a review in its original form, or in its proposed form, or side-by-side depending on whether the "Line" or "Parallel" link was selected.
......
When a "Line" link is clicked, a new browser window will come up with the contents of the file.
I am able to click on the Parallel. It pops up a new browser to show me both original and changed revision. However, the Line number next to the Parallel there is no hyperlink with it. Nothing poped up after I clicked on it. Can you please tell me how to fix it?
Thanks.
--- On Wed, 5/6/09, David Sitsky <dav...@gm...> wrote:
> From: David Sitsky <dav...@gm...>
> Subject: Re: No new browser window opened up after clicked on the line number.
> To: "Gary Yang" <gar...@ya...>
> Cc: cod...@li...
> Date: Wednesday, May 6, 2009, 5:45 PM
> The more recent versions of
> Codestriker removed the explicit
> underlines form the line numbers. If you click on
> them, a little
> inline popup window should appear, allowing you to enter a
> comment.
>
> If this is not happening, make sure you are at least using
> 1.9.8.
> Also try it with firefox, to make sure its not a browser
> issue.
>
> On Thu, May 7, 2009 at 10:00 AM, Gary Yang <gar...@ya...>
> wrote:
> >
> >
> > Hi David,
> >
> > I do not understand your explaination. From my
> understanding, the diff text matches the depot path. There
> is a hyperlinked parallel line. A window popped up after I
> clicked on the Paraelle. It shows two differen revisons of
> the file. I tried it again. Still, there is no hyperlink
> with the line number. Below is the detail.
> >
> >
> > in codestriker.conf:
> >
> > 'perforce:apache:apache1234@ipcswsvdcp4:1666',
> >
> > The Perforce client workspace spec:
> > p4 client -o
> > View:
> > //training/...
> //gary_pc_training/training/...
> >
> >
> > p4 diff -du
> > ==== //training/main.c#10 -
> c:\workspace\gary_pc_training\training\main.c ====
> > @@ -30,7 +30,6 @@
> >
> > #include <sys\ppc440sp_board.h>
> > #include <ppclib.h>
> > -#include <asynclib.h>
> > #include <stdio.h>
> > #include <sys\tcpiplib.h>
> > #include <serial.h>
> > @@ -41,12 +40,13 @@
> > /* SDRAM MICRON */
> > #define SDRAM_MICRON 0x2C
> >
> > -#define SDRAM_TRUE 1
> > +#define SDRAM_TRUE 2
> > #define SDRyAM_FALSE 0
> > #define SDRAM_DDR1 1
> > #define SDRAM_DDR2 2
> > #define SDRAM_NONE 0
> > #define MAXDIMMS 2
> > +#define max 3
> > #define MAXRANKS 2 /* Changes le 12/01/05 pour
> 1.6*/
> > #define MAXBANKSPERDIMM 8
> > #define MAXRANKSPERDIMM 2
> > ==== //training/test_dir/mainTG.c#1 -
> c:\workspace\gary_pc_training\training\test_dir\mainTG.c
> ====
> > @@ -20,8 +20,7 @@
> >
> #---------------------------------------------------------------------------*/
> > /* Perform DQS calibration and test memory */
> >
> > -#include <sys\ppc440sp_board.h>
> > -#include <ppclib.h>
> > +#include <ppc.h>
> > #include <asynclib.h>
> > #include <stdio.h>
> > #include <sys\tcpiplib.h>
> > @@ -34,6 +33,7 @@
> > #define SDRAM_MICRON 0x2C
> >
> > #define SDRAM_TRUE 1
> > +#define SDRAM_TRUE 9
> > #define SDRyAM_FALSE 0
> > #define SDRAM_DDR1 1
> > #define SDRAM_DDR2 2
> >
> >
> > Thanks,
> >
> >
> > Gary
> >
> > --- On Wed, 5/6/09, David Sitsky <dav...@gm...>
> wrote:
> >
> >> From: David Sitsky <dav...@gm...>
> >> Subject: Re: No new browser window opened up after
> clicked on the line number.
> >> To: "Gary Yang" <gar...@ya...>
> >> Cc: cod...@li...
> >> Date: Wednesday, May 6, 2009, 3:14 PM
> >> This happens when the diff you have
> >> loaded in doesn't match the
> >> repository associated with the topic. If you
> have the
> >> repository set
> >> to your Perforce depot, and the diff text matches
> the depot
> >> path, then
> >> those links will become active again. You'll
> need to
> >> create new
> >> topics whenever you change the repository string
> in
> >> codestriker.conf.
> >>
> >> Cheers,
> >> David
> >>
> >> On Thu, May 7, 2009 at 7:56 AM, Gary Yang <gar...@ya...>
> >> wrote:
> >> >
> >> > Hi David,
> >> >
> >> >
> >> > I use Perforce and Codestriker 1.9.6. In the
> The
> >> Codestriker Guide 1.9.5 at the section, 3.5.1.
> Viewing a
> >> Topic. The last paragraph says below:
> >> >
> >> > Each file is broken up into a series of
> "deltas". At
> >> the head of each delta block, for both the old and
> new
> >> versions of the file, there is an indication of
> what line
> >> number the delta started at. In this situation,
> clicking on
> >> the "Line 24" link on the left hand side, will
> open a new
> >> browser window, which will contain the complete
> original
> >> contents of codestriker/codestriker.pl, anchored
> at line 24.
> >> Clicking on the "Line 22" link on the right hand
> side will
> >> contain the complete contents of
> codestriker/codestriker.pl
> >> will all of the proposed changes applied.
> >> >
> >> > However, when I clicked on the line number,
> there is
> >> no new browser window opened up. Actually, there
> is no
> >> hyperlink line under the line number. It is
> different than
> >> what I see in the manual. Can you please let me
> know the
> >> reason?
> >> >
> >> >
> >> > Thanks,
> >> >
> >> >
> >> > Gary
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> >
> >
> >
> >
>
|