Oops - sorry didn't see your latest reply John - will investigate what you
mentioned
in your last reply.
Patrick
"Patrick McHale" <[EMAIL PROTECTED]> wrote in message
9hblhu$[EMAIL PROTECTED]">news:9hblhu$[EMAIL PROTECTED]...
> Yep - was a typo.
>
> Should have been Components.classes.Webterm has no properties.
>
> The problem still remains - the component is registered and appears in the
> about:plugins list.
> Everything is working and all of the xpcom functionality is operational -
> but still gives the same
> message in the debug window. Have since returned to New Zealand and
> installed Mozilla 0.9.1
> on my machine and the problem still exists. No idea where to proceed on
> this as everything is
> working - just the error message still remains... - don't know why.
>
> Patrick McHale
> Powerlan New Zealand
>
>
>
> "John Bandhauer" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > typo?
> >
> > your code samples said...
> > Components.classes["Webterm"]
> >
> > You've twice shown the error as...
> > Components.classes.webterm has no properties
> >
> > JS is case sensitive. Is this a typo in your code or your
> > message?
> >
> > No the JS interpreter (etc.) is not substantially different.
> > You've probably changed your code or not registered it correctly
> > in the new install.
> >
> > If you've changed the plugin code to register differently named
> > (in terms of contractids or interface names) components then
> > you'd need to force an autoregistration. This does not happen
> > automatically in release builds. regxpcom.exe will do this.
> > Removing your component.reg file and re-running mozilla is the
> > brute force way to do this. The same goes for changes xpt files
> > that reflect the interface information. The registration info for
> > them is generated into components/xpti.dat. You can delete that
> > file and rerun. Or just run regxpcom.exe and it will detect
> > changed xpt files and likely do the right thing.
> >
> > John.
> >
> > Patrick McHale wrote:
> > >
> > > MOZILLA_XPTI_REGLOG - sorry where is this?
> > >
> > > Also - The plugin is registered and operational. It appears in the
about
> > > plugins list. Everything seems fine and the plugin / xpcom stuff is
> > > working - yet still comes up with the error in the debug console
window.
> > >
> > > javascript error
> > > file :///c:/Mozilla/Locations/NS6Hollis.htm line 7:
> > > Components.classes.webterm has no properties.
> > >
> > > Seems strange that it should be giving this error message as it did
not
> do
> > > this until I upgraded to Mozilla 0.9. Everything else is working
fine.
> > > Does the javascript interpreter work differently under Mozilla 0.9.?
> > >
> > > Patrick McHale
> > > Powerlan USA
> > >
> > > "David Bradley" <[EMAIL PROTECTED]> wrote in message
> > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > > > Patrick McHale wrote:
> > > > >
> > > > > So how do you register it - attached is the javascript in a zip
> file.
> > > What
> > > > > have I missed in the javascript?.
> > > > >
> > > > > Thanks
> > > > >
> > > > > Patrick McHale
> > > > > Powerlan USA
> > > >
> > > > You should only have to put it in the components directory, is that
> > > > where's its living? Next try regxpcom that should register stuff.
Also
> > > > you might want to turn on logging on for auto registering to see if
> that
> > > > tells you anything. Do that by setting the MOZILLA_XPTI_REGLOG
> > > > environment variable to a file name.
>
>
