Bo Peng wrote:
PS. I don't like this way to insert labels. A) it seems prone for bugs,
B) the label is not shown on the screen.
PS2. I can't think of a good alternative right now.
Attached is a patch that fixes the bug. The only question I have is
whether or not CutAndPaste.cpp is the bes
Bo Peng wrote:
PS. I don't like this way to insert labels. A) it seems prone for bugs,
B) the label is not shown on the screen.
PS2. I can't think of a good alternative right now.
Attached is a patch that fixes the bug. The only question I have is
whether or not CutAndPaste.cpp is the bes
Vincent van Ravesteijn - TNW wrote:
We thought you were just talking about normal labels. So the problem
is that the mechanism that changes duplicate labels on copying isn't
working with the labels that go with listings child docs. That's what
we need to fix, since we don't want dup
>
> PS. I don't like this way to insert labels. A) it seems prone for bugs,
> B) the label is not shown on the screen.
>
> PS2. I can't think of a good alternative right now.
Attached is a patch that fixes the bug. The only question I have is
whether or not CutAndPaste.cpp is the best place to upd
Bo Peng wrote:
We thought you were just talking about normal labels. So the problem is
that the mechanism that changes duplicate labels on copying isn't working
with the labels that go with listings child docs. That's what we need to
fix, since we don't want duplicate labels.
Yep, I remem
>> We thought you were just talking about normal labels. So the problem
>> is that the mechanism that changes duplicate labels on copying isn't
>> working with the labels that go with listings child docs. That's what
>> we need to fix, since we don't want duplicate labels.
>
>Yep, I remember th
>> We thought you were just talking about normal labels. So the problem is
>> that the mechanism that changes duplicate labels on copying isn't working
>> with the labels that go with listings child docs. That's what we need to
>> fix, since we don't want duplicate labels.
>
> Yep, I remember this
Richard Heck wrote:
Bo Peng wrote:
Well, I'm using the 1.6.1 release..
.. and I really can't get two labels with the same name.
OK. I am using LyX svn/branch, svnversion 28539, flash screen shows
version 1.6.2svn.
Now repeat after me :-)
1. create a new document
2. insert File->Child d
Bo Peng wrote:
Well, I'm using the 1.6.1 release..
.. and I really can't get two labels with the same name.
OK. I am using LyX svn/branch, svnversion 28539, flash screen shows
version 1.6.2svn.
Now repeat after me :-)
1. create a new document
2. insert File->Child document->program list
>>3. insert cross-reference a.
>>4. select the listings inset, copy, paste,
>>5. click the copied listings. **I still see label a.**
>
> This is a bug.
>
> The label should have changed to "a-1" with a warning message (to be
> consistent with the 'normal' labels).
I see. The problem with InsetList
> Now repeat after me :-)
>
>1. create a new document
>2. insert File->Child document->program listing, with label a. (Fake
filename)
Here we differ.. I just inserted a program listing with "Insert->Program
Listing", sorry ;-)
>3. insert cross-reference a.
>4. select the listings inset, copy,
Bo Peng wrote:
Does it make sense to only do this if there is no Label_A in the
document? I copy listings inset around a lot so that I do not have to
re-specify some listings parameters, and the automatic change of
references have been annoying.
With the attached patch, only the update of
> Well, I'm using the 1.6.1 release..
>
> .. and I really can't get two labels with the same name.
OK. I am using LyX svn/branch, svnversion 28539, flash screen shows
version 1.6.2svn.
Now repeat after me :-)
1. create a new document
2. insert File->Child document->program listing, with label a.
>> If I copy a Listing with a label, the label is renamed to something
>> else in order not to have two labels with the same name. Then
renaming
>> this new label should not have any effect on the existing references.
>
>This is not the case for branch. I do not have trunk to test.
>
>Bo
>
Well
> If I copy a Listing with a label, the label is renamed to something else
> in order not to have two labels with the same name. Then renaming this
> new label should not have any effect on the existing references.
This is not the case for branch. I do not have trunk to test.
Bo
> Does it make sense to only do this if there is no Label_A in the
> document? I copy listings inset around a lot so that I do not have to
> re-specify some listings parameters, and the automatic change of
> references have been annoying.
With the attached patch, only the update of the 'first' Ins
>Dear list,
>
>If I have a document with a reference to a program listing,
>
>Ref:A Listing_with_Label_A
>
>If I copy Listing_with_Label_A to another listing and change
>its label to B. Ref:A will be automatically changed to B. That
>is to say
>
>Ref:B Listing_with_Label_A Listing_with
Dear list,
If I have a document with a reference to a program listing,
Ref:A Listing_with_Label_A
If I copy Listing_with_Label_A to another listing and change its label
to B. Ref:A will be automatically changed to B. That is to say
Ref:B Listing_with_Label_A Listing_with_Label_B.
Doe
18 matches
Mail list logo
