Re: [Gimp-developer] Macro Recorder 2nd Try

2003-06-24 Thread Hans Breuer
[already sent off-list by mistake] At 17:15 23.06.03 +0200, Sven Neumann wrote: Hi, Nathan Carl Summers [EMAIL PROTECTED] writes: In short the approach (more info in bugzilla) : - Intercept every PDB call if a macro recorder instance is running. The cvs version of Libpdb already provides a

Re: [Gimp-developer] Macro Recorder 2nd Try

2003-06-24 Thread Raphaël Quinet
On Mon, 23 Jun 2003 22:40:56 +0200, Hans Breuer [EMAIL PROTECTED] wrote: At 07:01 23.06.03 -0700, Nathan Carl Summers wrote: On Fri, 20 Jun 2003, Hans Breuer wrote: (try to guess the call stack depth to avoid recording functions called by a plug-in) I had a solution to that problem,

Re: [Gimp-developer] Macro Recorder 2nd Try

2003-06-24 Thread Sven Neumann
Hi, Hans Breuer [EMAIL PROTECTED] writes: But perhaps this just means that the Undo system needs to be hooked into the PDB as well ?! It would certainly be useful to have that capability. Though if the user is used to macro recording he would probably be able to change the brush selction

Re: [Gimp-developer] Macro Recorder 2nd Try

2003-06-23 Thread Sven Neumann
Hi, Nathan Carl Summers [EMAIL PROTECTED] writes: In short the approach (more info in bugzilla) : - Intercept every PDB call if a macro recorder instance is running. The cvs version of Libpdb already provides a flexible mechanism for intercepting pdb calls. I designed it with macro

Re: [Gimp-developer] Macro Recorder 2nd Try

2003-06-23 Thread Hans Breuer
At 07:01 23.06.03 -0700, Nathan Carl Summers wrote: On Fri, 20 Jun 2003, Hans Breuer wrote: I'm about to give it another try with current cvs code base, but before I would like to get some information to avoid (if possible) fast rotting bits. In short the approach (more info in bugzilla) :

Re: [Gimp-developer] Macro Recorder 2nd Try

2003-06-23 Thread Nathan Carl Summers
On Fri, 20 Jun 2003, Hans Breuer wrote: I'm about to give it another try with current cvs code base, but before I would like to get some information to avoid (if possible) fast rotting bits. In short the approach (more info in bugzilla) : - Intercept every PDB call if a macro recorder

Re: [Gimp-developer] Macro Recorder 2nd Try

2003-06-20 Thread Sven Neumann
Hi, Hans Breuer [EMAIL PROTECTED] writes: - Intercept every PDB call if a macro recorder instance is running. (try to guess the call stack depth to avoid recording functions called by a plug-in) That would mean that all actions go through the PDB. The fact is that no user action goes

Re: [Gimp-developer] Macro Recorder 2nd Try

2003-06-20 Thread Hans Breuer
At 15:20 20.06.03 +0200, Sven Neumann wrote: Hi, Hans Breuer [EMAIL PROTECTED] writes: - Intercept every PDB call if a macro recorder instance is running. (try to guess the call stack depth to avoid recording functions called by a plug-in) That would mean that all actions go through

Re: [Gimp-developer] Macro Recorder 2nd Try

2003-06-20 Thread Raphaël Quinet
On Fri, 20 Jun 2003 16:50:37 +0200, Sven Neumann [EMAIL PROTECTED] wrote: Hans Breuer [EMAIL PROTECTED] writes: This is the all-or-nothing argument. IMO a macro recorder would already be useful if it only records the calls done as reaction on users menu usage, where many go through the