Use a consistent naming pattern for moving averages in the VectorVest Fields group.

Currently, there are two patterns:

CI ## Day MA

## Day MA(RT)

I personally like the CI naming pattern, because the field would be clustered with other fields using the same base measure.

L'Oreal is a 72 B market cap stock which should be in VectorVest.

Place these watch lists for Splendid SPYDers in the standard program so we do not need hours to develop them ourselves., as good as that training might be.

I would like to see the BackTest's Trade History allow a Graph to open to the trade dates, open-to-close. If the trade (especially from a backtest) was June 5 to Sept 20, show the graph from June 5 to Sept 20.

This avoids an excessive manual step, to locate the trade timeframe. One can inspect other graph layouts, and may need to expand the time window slightly, to see chart warning signs.

This feature would be the alternative to manually scrolling/expanding/contracting, to the trade timeframe that needs to be inspected.

The number of New Shares issued directly affects Price. When new shares are issued, Price drops accordingly (see AGNC on 12/9/2010). But VV's data display is late, thereby making it impossible to correlate the relationship between New Shares issued & Price. Can't VV display the data in a more timely fashion to enable trading and searching based on this phenomenon?

Whenever a popup screen appears – it is not centered upon the parent window; the location of the popup window on the screen is random – this is just a usability issue. If the popups can be centered on top of their parents – the navigation will be simpler.

It would nice to be able to add columns on the VV7 home page. I've dedicated one of my 24 inch monitors to VectorVest and that leaves a lot of real estate to take advantage of an extra column for minigraphs of selected stocks, indexes, etc. I realize that I can create tear-off graphs for those and position them beside the RealTime program window, but the positons are not remembered when the program is next started so the operation has to be redone on each restart.