Jean-Marc Lasgouttes wrote:
> Guenter Milde writes:
> >> how you want to do it more helpful? when i need new branch inset i want to
> >> do it directly by one menu click.
> >
> > How about a unified functionality that would also fix bugs 4462 and 5851:
>
> This seems to be a better way to proceed
Hi,
Something I would have found useful when I used branches doing my CV was
the ability to enable/disable several branches at once. The CV was a good
place to use branches, as it easily allowed different parts to be swapped
in and out. However, I wasn´t able to do it all in different branches
Guenter Milde writes:
>> how you want to do it more helpful? when i need new branch inset i want to
>> do it directly by one menu click.
>
> How about a unified functionality that would also fix bugs 4462 and 5851:
This seems to be a better way to proceed, IMO. Define add 'Other...' to
Insert>Bra
Jean-Marc Lasgouttes wrote:
> > would you be satisfied if this was the default menu action while the lfun is
> > still able to do it for the lazybones like me?
>
> What I dislike is that you rely on a special branch name to be a keyword
> for another action.
but thats exactly what i need :(
pavel
Pavel Sanda writes:
> Jean-Marc Lasgouttes wrote:
>> having menu entries which
>> do only one thing has some merit in terms of clarity.
>
> would you be satisfied if this was the default menu action while the lfun is
> still able to do it for the lazybones like me?
What I dislike is that you rel
On 2009-03-18, Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
>> Pavel Sanda writes:
>> >> What is this branch_inset_insert thing. It looks kind of wrong.
>> >
>> > the purpose is to automatically insert the branch inset after establishing
>> > new branch.
>> I am not so sure that this is help
Jean-Marc Lasgouttes wrote:
> having menu entries which
> do only one thing has some merit in terms of clarity.
would you be satisfied if this was the default menu action while the lfun is
still able to do it for the lazybones like me?
pavel
Pavel Sanda writes:
> how you want to do it more helpful? when i need new branch inset i want to
> do it directly by one menu click.
Having one-click way to define a new branch type and insert a branch
inset of this type is not on my personal list of life-saving features.
Two clicks would not be
Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
> >> What is this branch_inset_insert thing. It looks kind of wrong.
> >
> > the purpose is to automatically insert the branch inset after establishing
> > new branch. bit hackish, yes, but i didn't find better way how to do it.
> > perhaps you hav
Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
> > - introduce actvation/deactivation through the context menu
> > (2 JMarc - i tried your proposal through branch-activate lfun, but
> > when i come to thepoint when i needed to copy the whole code from
> > next-inset-toggle lfun i returned
On 2009-03-16, Richard Heck wrote:
> Guenter Milde wrote:
>> On 2009-03-16, Pavel Sanda wrote:
>>> the attached patches:
>>> - introduce new menu item for defining new branch, so you can directly
>>> put new branch into the document.
I do not know where the new item is currently inserted, but p
Pavel Sanda writes:
>> What is this branch_inset_insert thing. It looks kind of wrong.
>
> the purpose is to automatically insert the branch inset after establishing
> new branch. bit hackish, yes, but i didn't find better way how to do it.
> perhaps you have some idea?
I am not so sure that this
Vincent van Ravesteijn wrote:
>>> Why not branch-new-insert ? This one can fire branch-new.
>>>
>>
>> now you are talking about lfun or parameter name?
>>
> LFUNs yes.
hmm i somehow didn't like the overpopulation - we would have
branch-insert, branch-new-insert, branch-new.
pavel
ps: i h
Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
Pavel Sanda schreef:
Richard Heck wrote:
What does one already do to insert a branch inset? Can't we just use
that, and if the name given isn't already known, add it to the branch
list?
the problem here that w
Vincent van Ravesteijn wrote:
> Pavel Sanda schreef:
>> Richard Heck wrote:
>>
>>> What does one already do to insert a branch inset? Can't we just use
>>> that, and if the name given isn't already known, add it to the branch
>>> list?
>>>
>>
>> the problem here that we dont know the name
Pavel Sanda schreef:
Richard Heck wrote:
What does one already do to insert a branch inset? Can't we just use that,
and if the name given isn't already known, add it to the branch list?
the problem here that we dont know the name user has given to us,
so command-sequence etc can't be u
Richard Heck wrote:
> What does one already do to insert a branch inset? Can't we just use that,
> and if the name given isn't already known, add it to the branch list?
the problem here that we dont know the name user has given to us,
so command-sequence etc can't be used.
pavel
Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
i started to use branches lately and i found out that our UI for them
is bit annoying since every other change needs tobe done through
preferences dislog.
the attached patches:
- introduce new menu item for defining new branch, so you can direct
Jean-Marc Lasgouttes wrote:
> > i started to use branches lately and i found out that our UI for them
> > is bit annoying since every other change needs tobe done through
> > preferences dislog.
> >
> > the attached patches:
> > - introduce new menu item for defining new branch, so you can directly
Pavel Sanda writes:
> i started to use branches lately and i found out that our UI for them
> is bit annoying since every other change needs tobe done through
> preferences dislog.
>
> the attached patches:
> - introduce new menu item for defining new branch, so you can directly
> put new branch
Pavel Sanda writes:
> - introduce actvation/deactivation through the context menu
> (2 JMarc - i tried your proposal through branch-activate lfun, but
> when i come to thepoint when i needed to copy the whole code from
> next-inset-toggle lfun i returned to the idea of enhancing
> our own
Guenter Milde wrote:
On 2009-03-16, Pavel Sanda wrote:
the attached patches:
- introduce new menu item for defining new branch, so you can directly
put new branch into the document.
Great.
- introduce actvation/deactivation through the context menu
Great as well.
How d
On 2009-03-16, Pavel Sanda wrote:
> the attached patches:
> - introduce new menu item for defining new branch, so you can directly
> put new branch into the document.
Great.
> - introduce actvation/deactivation through the context menu
Great as well.
How does it behave in a parent/child set
hi,
i started to use branches lately and i found out that our UI for them
is bit annoying since every other change needs tobe done through
preferences dislog.
the attached patches:
- introduce new menu item for defining new branch, so you can directly
put new branch into the document.
- introdu
24 matches
Mail list logo
