Abdelrazak Younes writes:
>> OK, I agree it should not. But how do I do that? The dispatch mechanism
>> supposes today that I have set the cursor in the bufferview.
>
> First make a method Buffer::insetForAll(DocIterator beg, DocIterator
> end) that will use a . Then implements two LFUN_INSET_FORA
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes writes:
Jean-Marc Lasgouttes wrote:
A few questions remain:
* if I use "inset-forall Note inset-toggle close", this fails in the
case of a note in a note. I still do not know why
* for each inset, lyx::dispatch is invoked with the curs
Abdelrazak Younes writes:
> Jean-Marc Lasgouttes wrote:
>> A few questions remain:
>>
>> * if I use "inset-forall Note inset-toggle close", this fails in the
>> case of a note in a note. I still do not know why
>>
>> * for each inset, lyx::dispatch is invoked with the cursor in front of
>> th
Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
> > > this number is max changes done, right? if so i would make bigger
> > > if waiting time is not much (or set it up, so the current processors
> > > doesn't wait more then - say - 5sec?)
> >
> > I will experiment, but it seemed to me that my ori
Jean-Marc Lasgouttes wrote:
> > this number is max changes done, right? if so i would make bigger
> > if waiting time is not much (or set it up, so the current processors
> > doesn't wait more then - say - 5sec?)
>
> I will experiment, but it seemed to me that my original 1 value was
> too lar
Jean-Marc Lasgouttes writes:
>> could you be more verbose how does it differ from users pov?
>
> One can only execute functions that are available when the cursor is in
> front of the inset. For example, one cannot change the type of a note, I
> think, because the inset at point never sees the req
Pavel Sanda writes:
> this number is max changes done, right? if so i would make bigger
> if waiting time is not much (or set it up, so the current processors
> doesn't wait more then - say - 5sec?)
I will experiment, but it seemed to me that my original 1 value was
too large. O course, this
Jean-Marc Lasgouttes wrote:
> Here is the second iteration of my inset-forall patch. This version
> allows for matching all insets with the syntax
> inset-forall * cmd args
> and for matching insets names with spaces
> inset-forall "inset name" cms args
nice nice nice :)
> Another new 'featur
rgheck writes:
> On 12/02/2009 04:30 AM, Jean-Marc Lasgouttes wrote:
>> * if I use "inset-forall Note inset-toggle close", this fails in the
>>case of a note in a note. I still do not know why
>>
>>
> Do you mean that it fails to close the outer inset, or the inner one?
Both.
> Does thi
On 12/02/2009 04:30 AM, Jean-Marc Lasgouttes wrote:
* if I use "inset-forall Note inset-toggle close", this fails in the
case of a note in a note. I still do not know why
Do you mean that it fails to close the outer inset, or the inner one?
Does this code enter the insets? I.e., suppose
Jean-Marc Lasgouttes writes:
> Here is the second iteration of my inset-forall patch. This version
> allows for matching all insets with the syntax
> inset-forall * cmd args
> and for matching insets names with spaces
> inset-forall "inset name" cms args
>
> To this end, I have added a FuncRe
Here is the second iteration of my inset-forall patch. This version
allows for matching all insets with the syntax
inset-forall * cmd args
and for matching insets names with spaces
inset-forall "inset name" cms args
To this end, I have added a FuncRequest::getLongArg, that I will commit
separ
12 matches
Mail list logo
