Code References Version 1.2 Beta

38236
Project ManagerJim Nelson

Click here to download

CodeReferences2.png

Enhancement in this release (since 1.1 Beta)
  • There is a new 'Code Filter' box at the top of the form, which acts as a filter on the Code column in the grid. This performs a case-insensitive search ($) and remains in effect until removed.
  • Class libraries listed in the TreeView on the left have sub-nodes corresponding to all the individual classes within them.
  • All files opened by double-clicking on the results grid update the appropriate VFP MRU list, and the case of the file names is maintained.
  • Drop-down list of projects uses the VFP MRU list of projects (instead of only those that are open). Selecting a project from the list will open that project if it is closed.
  • There are two new options in the Options form:
    • Files opened by double-clicking on the results grid can be checked out using Source Control.
    • Files listed in the TreeView on the left can be listed with their folder names (relative to the project or current folder).

Summary of All Enhancements

Search Screen:
  • CommandButton to select current folder
  • Drop down list for ‘Scope’ includes the entire VFP MRU list of projects. Selecting a project from the list will open that project if it is closed.
  • The search form is now re-sizable (well, at least, it can be made wider).
  • Changes to file templates:
    • Searching for blanks in file names now supported
    • Blanks no longer supported as delimiters between templates; valid separators are comma and semi-colon

New Searching Capabilities:
  • Included in search:
    • Class names (searches now done on Class and ClassLoc columns of VCX/SCX files)
    • Names of PRG files
  • Regular expressions recognize continuation lines

Results Screen:
  • Dockable; retains docking information in new session
  • Does not allow items to be checked for replacement if they can’t be replaced:
    • Method and procedure names, etc, (as before)
    • Regular expressions (unless using no special characters)
  • File names are shown as relative to the project or current directory
  • Some re-arrangement of display between the ‘class’ and ‘method’ columns; new values in ‘method’ column
    • <Class Def>
    • <Class>
    • <Property Def>
    • <Property>
    • <Method Def>
    • <Method>
    • <PRG File>
    • <Include File>
    • <Object>
    • <Procedure>
    • <Function>
  • A new 'Code Filter' box at the top of the form acts as a filter on the Code column in the grid. This performs a case-insensitive search ($) and remains in effect until removed.
  • All files opened by double-clicking on the results grid update the appropriate VFP MRU list, and the case of the file names is maintained.
  • Changes in the TreeView
    • Class libraries listed in the TreeView on the left have sub-nodes corresponding to all the individual classes within them.
    • A new option (Options form) causes files list in the TreeView to be listed with their folder names (relative to the project or current folder).
  • New column displays timestamp:
    • For VCXs and SCXs, the timestamp from row of source file
    • For all other sources, the timestamp of source file
  • Cascading (i.e., multi-column) file sorts
  • New sort options, by Folder or Extension, now available from right-click context menu on the grid cells.
  • Sorting now allowed on ‘Code’ column

Options form
  • Files opened by double-clicking on the results grid can be checked out using Source Control.
  • Files listed in the TreeView on the left can be listed with their folder names (relative to the project or current folder).

Bug Fixes:
  • Minor bug with Whole Word not matching word starting at beginning of file / method
  • Column width had not been preserved between sessions for one of the columns

Other / Miscellaneous:
  • Install / uninstall programs
  • Files that are opened are recorded in ‘MRU Files’ in PEM Editor (if open)
  • Version # displayed
  • Uses own resource file – in Home(7)
  • Processing time is displayed in a WAIT WINDOW

Release History:
  • Ver 1.2 Beta - Released 2010-10-09
  • Ver 1.1 Beta 2 - Released 2010-05-17 (430 downloads)
  • Ver 1.1 Beta 1 - Released 2010-04-13 (187 downloads)

Last edited Oct 10, 2010 at 3:48 AM by JimRNelson, version 18

Comments

petersomers Jan 12, 2012 at 6:00 PM 
Hi, I'm getting a C5 error "OLE Exception error C5" when I try to edit a found program from the app

JimRNelson May 27, 2011 at 3:50 AM 
Mike -- You can also change the dockable setting by right-clicking on the TitleBar / Jim

MikePotjer May 23, 2011 at 1:59 PM 
These are some very nice enhancements. I really like the fact that the Code References form now utilizes the Dockable property. Unfortunately, the default value being used for Dockable is 2, and the Code References interface doesn't provide a way to change it. However, here is a simple tip to change the Dockable setting of the Code References results form:
1. Open the Code References form.
2. In the Command Window, enter the following: _ofoxref.Dockable=1

Now the main Code References form can be moved outside the VFP IDE (such as to a different monitor), and the new Dockable setting will be saved and restored the next time you open the form.

JimRNelson May 26, 2010 at 3:42 PM 
RE: getting no search results

In the search screen, there is a drop-down combobox of which file types to search. Even though that display may look correct, please try re-selecting it and running your search again. I believe that will solve the problem.

ljr1981 May 26, 2010 at 3:36 PM 
Jim sent me the following message in my email: "In the search screen, there is a drop-down combobox of file which file types to search. Even though that display may look correct, please try re-selecting it and running your search again."

This works and I only had to do it one time. All subsequent searches work as-is with no need to adjust anything. Thanks for the timely and helpful responses Jim. The tool is now working very well!!

ljr1981 May 26, 2010 at 3:26 PM 
I reinstalled the beta and did a search for "goApp" as this global variable is used extensively in our system. On the old VFP code ref app, there are many returns. In the beta version it reports that it took 0.2xx seconds to search, but has no return values whatsoever. The settings are the default, so I am making no changes to how the app is told to search. i am not using regular expressions or anything else unusual. The code is in a PJX file, which is under control by VSS (e.g. the project file is joined to a VSS source control project). I am not sure what else I can tell you about it. Only thing I can suggest is perhaps a SET STEP at some location in the code where you expect a search to initiate and run and see what happens.

ljr1981 May 26, 2010 at 3:21 PM 
OK -- the SQL: Order by clause error has now been dealt with. Thank you for the tip on how to handle that. I will try to reinstall the beta version and see if I can reproduce the error.

JimRNelson May 26, 2010 at 3:14 PM 
Yes, there is a problem with the uninstall ... what you can do is to select 'Ignore' until it goes away, and then when you get your results display, click on one of the column headings. Thereafter, you should have no problems.

As for getting no search results -- this is most mystifying. I have one other such report. Can you supply more information, as I would really like to track this down. Contact me at JimRNelson@GMail.Com

ljr1981 May 25, 2010 at 5:07 PM 
I get no search results even after performing a cleanup of the source tables (under options). VFP was restarted right after the installation. What is a bit annoying is that uninstall has left my stock VFP code ref tool with the same error: SQL: Order by clause is invalid.

JimRNelson Apr 14, 2010 at 6:56 PM 
Best way to do so is under "Discussions" or "Issues" -- as then I receive an email automatically when you do so.

Goofus828 Apr 13, 2010 at 1:35 PM 
Hi - Downloaded this yesterday and I like it!
I am seeing some issues though. Where do I post suspected bugs?