From: John Stone (johns_at_ks.uiuc.edu)
Date: Mon Sep 25 2006 - 07:48:33 CDT

Rob,
  If you started with the versions in the VMD source tree,
then yes, cranking the minor version number by one should do it:
e.g.:
  0, /* major version */
  2, /* minor version */

change to:
  0, /* major version */
  3, /* minor version */

  John

On Mon, Sep 25, 2006 at 05:33:43AM -0700, Rob wrote:
>
>
> --- John Stone <johns_at_ks.uiuc.edu> wrote:
>
> >
> > Rob,
> > If you recompile the VASP plugins after _updating
> > their internal version numbers_ VMD will indeed
> > load them...
> > Try cranking the minor version numbers on your
> > plugins, then recompile, and VMD should load your
> > new ones just fine.
>
> Just double check:
> At the bottom of the plugins, there is this
> molfile_plugin_t variable with the list of numbers
> and pointers-to-functions etc.
> Bumping the minor version here from 2 to 3 would
> make the executable load the newer plugins?
>
> I'll try it soon and will then submit patches to
> the current plugins.
>
> Cheers,
> Rob.
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com

-- 
NIH Resource for Macromolecular Modeling and Bioinformatics
Beckman Institute for Advanced Science and Technology
University of Illinois, 405 N. Mathews Ave, Urbana, IL 61801
Email: johns_at_ks.uiuc.edu                 Phone: 217-244-3349
  WWW: http://www.ks.uiuc.edu/~johns/      Fax: 217-244-6078