[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: patch for much more stable nsplugins
From:       Richard Bos <allabos () freeler ! nl>
Date:       2001-01-27 7:55:15
[Download RAW message or body]

On Thursday 25 January 2001 22:10, Wynn Wilkes wrote:
> > > > > > I've tested this for around 15 minutes with different web sites,
> > > > > > especially with Flash 4 and Plugger. I wasn't able to get any
> > > > > > crash anymore. Even www.newgrounds.com seems to work fine now.
> > > > > > Please check it out. If nobody objects until tomorrow I will
> > > > > > commit it.
> > > > >
> > > > > Are we by default doing artsdsp nspluginviewer, now?
> > > >
> > > > It's commented out. I enabled it locally but it sucks (read: arts
> > > > output is stuttering). Can someone please look at this (/me looks as
> > > > Stefan W. ;)
> > >
> > > That's better than Konqueror locking up, the plugin never appearing.
> > > and me being forced to kill artsd, or kill nspluginviewer, no?
> >
> > I agree. Maybe it would have been best to add a checkbox to the arts
> > and/or nsplugin kcontrol module. But as the next release is waitung just
> > behind the next door, it's a bit late. Maybe next time....
>
> Couldn't you put in the code to check the KConfig object for artsdsp
> options, and make it a hidden option for now, and add the gui configuration
> part after 2.1?  It would be very nice- people could edit their own
> kcmnspluginrc to add a boolean option for UseArtsdsp...if they have a
> working artsdsp setup.

Is the nsplugins directory in kdebase compiled by default, or should it done 
manually.  At my system the directory is not compiled.  When I compile it 
manually it gives an compile error.

-- 
Richard Bos
For those who have no (/)home the journey is endless

[prev in list] [next in list] [prev in thread] [next in thread]