[Gtkradiant] Second possible problem with 1.2.1-nightly

Timothee Besset gtkradiant@zerowing.idsoftware.com
Tue, 15 Jan 2002 10:01:25 +0100

The refresh command is a remnant from the first plugin implementations in
QERadiant. Even at that time it was not properly supported, because
nothing forced you when you were writing the plugin to support the
functionality. Now what we 'could' do, is have a seperate API for plugin
refresh, and ask the plugins we load wether they support the feature.

The only use I could see to this is during plygin developement, which
would allow you to rebuild a new bin and reload it without closing the
editor. Given binary files locking on win32 I'm not even sure this is
possible. And we are not in a situation where we want to have maximum
uptime of the editor while we are developing for it. .. so I say .. it can
safely go away.


On Tue, 15 Jan 2002 03:11:44 +0100
"Hydra" <hydra@hydras-world.com> wrote:

> agreed, does anyone ever use refresh ?  and if so, why ?
> ----- Original Message ----- 
> From: "Timothee Besset" <ttimo@idsoftware.com>
> To: <gtkradiant@zerowing.idsoftware.com>
> Sent: Monday, January 14, 2002 10:55 PM
> Subject: Re: [Gtkradiant] Second possible problem with 1.2.1-nightly
> > We should probably remove the 'refresh'. It doesn't work, specially when
> > it's modules and not plugins, and we don't really have any intention to
> > make it work either. Who's doing this? ;-)
> _______________________________________________
> Gtkradiant mailing list
> Gtkradiant@zerowing.idsoftware.com
> http://zerowing.idsoftware.com/mailman/listinfo/gtkradiant