Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#66 No method navigator

closed
nobody
Editor (71)
8
2003-11-02
2003-10-31
Kannan Ekanath
No

Hi,
I am currently using J-0.20.1 but i am not able to see a
method navigator in the screen. Earlier i was able to see
but now it is not there. Is it a know issue. I need the
method navigator below desperately
Thanks

Discussion

1 2 > >> (Page 1 of 2)
  • Peter Graves
    Peter Graves
    2003-10-31

    Logged In: YES
    user_id=558172

    Maybe you have the sidebar turned off. Go to the View menu
    and make sure the "Sidebar" checkbox is checked.

    Or does the sidebar appear, but without the method navigator?

    If you still have a problem:
    1. What mode? (Java, Lisp, C, etc., or all modes?)
    2. What version of Java are you using?
    3. What operating system?

    There is no known problem with the sidebar or method navigator.

     
  • Peter Graves
    Peter Graves
    2003-10-31

    • status: open --> pending
     
  • Kannan Ekanath
    Kannan Ekanath
    2003-10-31

    Logged In: YES
    user_id=840658

    Well piso,
    The sidebar is turned on. It is showing the file navigator.
    I opened a java file and could not see a method navigator
    (did you mean this by mode?)

    Java SDK 1.4.2 and OS is Windows

     
  • Kannan Ekanath
    Kannan Ekanath
    2003-10-31

    • status: pending --> open
     
  • Kannan Ekanath
    Kannan Ekanath
    2003-10-31

    Screen shot is also attached please unzip and see

     
    Attachments
  • Kannan Ekanath
    Kannan Ekanath
    2003-10-31

    Logged In: YES
    user_id=840658

    Please also find an attached screen shot

     
  • Peter Graves
    Peter Graves
    2003-10-31

    Logged In: YES
    user_id=558172

    I see what you mean.

    You might try getting rid of the files C:\.j\props and
    C:\.j\props~ (if it exists) and then restarting j.

    If that doesn't work, try moving the entire C:\.j directory
    out of the way (rename it to C:\.xj or something). Do you
    have anything in C:\.j\prefs?

    Do you have the same problem with 0.20.2?

     
  • Kannan Ekanath
    Kannan Ekanath
    2003-10-31

    • priority: 5 --> 8
     
  • Kannan Ekanath
    Kannan Ekanath
    2003-10-31

    Logged In: YES
    user_id=840658

    Now this sounds quite ununderstandable.

    I have a folder called d:\java\j-0.20.1 where all are installed.
    This has got the followign
    doc (folder-having htmls)
    examples (two lisp files)
    themes (some other files)
    COPYING (unknow file...windows does not know what
    application to associate with)
    j.jar

    these are the only files over there.
    in the command line i type
    C:\> java -jar d:\java\j-0.20.1

    this is showing up a screen like the one i gave you.

    I remember seeing it initially....but am not able to figure out
    what you mean by saying .j/prefs and all those files

    I tried j-0.20.0 then 20.2 and then 20.1 all are giving the
    same problem..also the look and feel of 20.2 looks the same
    as 20.1 but in my nearby computer the entire look and feel is
    different. i am going hayweird

     
  • Peter Graves
    Peter Graves
    2003-10-31

    Logged In: YES
    user_id=558172

    By defaut, j stores its state in one or more files in the
    folder C:\.j (on Windows). My guess is that somehow or other
    your state files have been corrupted (for lack of a better
    term).

    So I'm suggesting that you move the entire C:\.j folder
    somewhere else, so you end up with no C:\.j folder on your
    system. Basically, you need to do something like this:

    rename C:\.j C:\.xj

    (I don't run Windows, so I'm not sure I've got the syntax
    just right.)

    Worst case, you could drag the C:\.j folder to the recycle
    bin. You'd lose your prefs file, but you don't seem to know
    what that is, so you probably don't have one.

    Then restart j and see if the problem goes away.

    It would probably be better to do this with 0.20.2, since
    it's the current version. I don't remember any bug in 0.20.1
    that would account for this behavior, however.

     
1 2 > >> (Page 1 of 2)