On 7/3/07, Chachereau Nicolas <[EMAIL PROTECTED]> wrote:
This starts filerx and tells it which instance it is supposed to talk to. The X window ID isn't useful for this purpose, what a director started from SciTE would need is the name of the pipe SciTE is listening to. We could simply call this $(PipeName)
As Neil mentionned in a previous email, we should be careful about this. Activating (the word X uses for that, i.e. giving a window the focus and raising it above the others) can be really annoying for a user, for example if a window is suddenly activated while we were doing something else.
Yeah, but how real a problem is this? The typical situation is that you are working with the Director program, and it wants to bring up SciTE to show us a file (like scitePM). Having an extension running in the background which brings up SciTE is just bad-mannners.
Doesn't anyone have some comments about my remarks in DirectorExtension.cxx? Steve, you only commented on one of them.
//TODO: is it really good to exit like this?
Well, up to now that's the way we've always been exiting ;) But seriously, the director has lanched SciTE and we are in an unrecoverable position; why not just quit?
// If we keep the exit call, we shouldn't call it with 0...
Absolutely. The director should be able to check this and go Oh No!
// TODO: should we really use ipc.scite.name even if not started by director?
Good question. To be consistently backward-compatible, one shd bail out. But I thought that assymmetrical extensions (those that just want to drive SciTE and not listen) are quite legitimate.
// TODO: store the file name in a property?
Absolutely! The x11.windowid is actually something else altogether. ScitePM needs it for its own bring-SciTE-to-front. But then that will be handled properly... steve d. _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
