Re: [scite] stage #1 - job queue encapsulation within a class

2005-10-25 Thread Neil Hodgson
April White: > >>2. implement a means whereby a direct call to Execute() is unnecessary > >> > >> > > I don't understand what you are planning here? > > > > > This is based on something you wrote some time back, in the "exposing > the SciTE 'execute tool' functionality to Lua'. I quote you as:

Re: [scite] stage #1 - job queue encapsulation within a class

2005-10-25 Thread Neil Hodgson
Robert Roessler: > Aw, gee, just one little pure-virtual class (say, SciMutex?) with > platform-specific derived classes (SciMutexWin32, SciMutexGLib, and > SciMutexNone) should cover it... :) And fix up all the build/make files. If you or April want to then go ahead. Neil ___

Re: [scite] stage #1 - job queue encapsulation within a class

2005-10-25 Thread April White
Neil Hodgson wrote: > The UI thread monitors this and when there is a command here and > no tool thread running, it moves a command into the main command > queue and starts the tool thread. ... When the thread exits, it should post a message to SciTE (like it does now) as that is a good